3 ms·
I agree. I'm developing a system which uses webapp to interact with device over USB. It works in Chrome. It's sad for me to not support Firefox but the only way
by vbezhenar 4y ago
I agree. I'm developing a system which uses webapp to interact with device over USB. It works in Chrome. It's sad for me to not support Firefox but the only way is to ask user to run some binary which will open websocket on localhost to interact with USB device. This is strictly worse from security PoV. This is strictly worse from usability PoV (user have to download and install manually additional component). This introduces update hurdles (I need to develop reliable updater). So much friction and issues just because of purity stand which hurts user in the end.
- dmitriid 4y ago> I'm developing a system which uses webapp to interact with device over USB. It works in Chrome. It's sad for me to not support Firefox As a cautionary tale: the moment Firefox shipped support for a hardware API they immediately ran into sites abusing them. Of course, Chrome doesn't even hide them behind a user prompt. https://twitter.com/denschub/status/1582730985778556931 https://twitter.com/denschub/status/1582730985778556931 (and comment) There are reasons Firefox opposes these standards. Chrome is neither your friend nor does it care for the web. Why are you so willing to give a carte blanche to a power struggle (Chrome/Web vs. Android) inside a web advertising company is beyond me.
- vbezhenar 4y agoI don't know about MIDI but accessing USB requires user confirmation and you can only access a selected port.
- dmitriid 4y agoThat's why th ecautionary tale: which of the capabilities of those APIs whould be behind user consent and which shouldn't? At which point will the user just click "yes" without reading those consent pop ups?