Friend gave me access to his Adobe account (I’m never giving Adobe money again), and it looks like they don’t even support Firefox. That means I’m not using even the one remaining browser-based Adobe service that’s left.
Friend gave me access to his Adobe account (I’m never giving Adobe money again), and it looks like they don’t even support Firefox. That means I’m not using even the one remaining browser-based Adobe service that’s left.
It’s because they’re using a chrome only API to interact with USB devices. This used to be a dedicated piece of software. I guess they don’t even want to provide an electron app.
deleted by creator
Honestly, I kinda hate the idea of a browser being able to access hardware devices.
That’s why no one outside Google wants it. Apple said no. Firefox said no. There’s a reason. WebRTC is shit. It leaks too much just for a small convenience.
And yeah, browsers don’t need my USB ports thanks.
This move was what hurt VIA as they moved to the API exclusively. So the only native apps are just electron wrappers 🤷♂️
Edit: Looks like Mozilla said yes after all heavy sigh: https://developer.mozilla.org/en-US/docs/Web/API/WebUSB_API
At the end we have Flash + ActiveX alltogether again.
WebRTC and WebUSB are different things. RTC doesn’t provide direct port access, afaik.
I know. Both have the same fundamental premise: to leak data that shouldn’t be leaked.
“WebUSB provides a way for these non-standardized USB device services to be exposed to the web. This means that hardware manufacturers will be able to provide a way for their device to be accessed from the web, without having to provide their own API.”
That’s from Mozilla. And that’s a hard pass. Why anyone wants this is beyond me. Just so long as there’s a flag to turn it off.
Have you worked with either before? They’re completely unrelated technologies, with similar names. They have nothing to do with one another. They’re not even being developed by the same groups. They emphatically do not have the same fundamental premise. I’ve built apps in WebRTC before, and I can guarantee it has nothing to do with WebUSB, and in fact I just confirmed in the docs that it has nothing to do with any sort of device-level hardware control.
To reiterate: the only connection between WebUSB and WebRTC is the fact that they’re named “Web” + three letter initialism.
Wikipedia is pretty aggressive with these bots
I have absolutely no idea what that’s intended to mean.
That’s their web dev documentation. The official position is no: https://mozilla.github.io/standards-positions/#webusb
Is this an app for recording and editing podcasts? Why do they need usb access for that? On its website it doesn’t says anything about usb.
Microphones, webcams, capture cards, etc
those do not require access to the underlying devices to get tho
What do they need that for? Every bowser has a file picker/dragndop.
I see it as them interacting directly with microphones, webcams, and other peripherals.
Every browser manages that too, though.