Post #1953759
2026-04-20 03:11 UTC
@r Sorry, I understand the goal, but it's the worst possible approach, allowing USB device access from a web browser.
Write an intermediary that you can have the source code to and trust, to talk to your device (with permission) and publish a local https service, and you can browse to localhost:7575 to control/monitor it.
That's the right model.
Replies (2)
-
@r@glauca.space 2026-04-20 03:15
@jab01701mid that's more-or-less precisely how this works (except it uses the WebExtensions "native messaging" capacity, which can be safer than using a localhost HTTP connection)
-
@nik@toot.teckids.org 2026-04-20 18:21
@jab01701mid @r Correct. But right now we're at "Google supports it, so let's use it", so every Android ROM installer or robot tinkering site for kids or you name it basically tells people to switch to Chrome. We're better off telling them to install a Firefox extension, although I'd prefer telling them to not use a browser to control local hardware but that's off the table I suppose.