News for hackers. Stuff that matters.

ultimatt42

Re:Show HN: I built an HTML5 RTL-SDR application on Thursday December 12, 2024 @05:26PM (#42404066)
> depending on your OS, an "Arduino.exe" can't even access USB devices without an additional signed driver and/or further administrative privileges

Which OS are you thinking of? WebUSB doesn't need any additional drivers, so if the browser can do it I assume any app can do it.

No, Logitech mice and keyboards generally use Logitech's proprietary HID++ protocol which is built on top of standard HID. WebUSB considers HID a "protected interface class" and blocks access to USB HID interfaces. USB HID devices are protected because they include devices like keyboards which handle sensitive user data, such as passwords.

https://wicg.github.io/webusb/#has-a-protected-interface-cla...

WebHID also restricts access to mice and keyboards, but it uses information available at the HID protocol level to selectively block access to sensitive capabilities while leaving other capabilities unblocked. So, you can't implement an input logger but you can configure LEDs and other device behavior.

In general, WebUSB isn't useful for devices that already have some system-level support. If there's a driver, it will have already claimed the USB interface and needs to release it before the browser can access it. Even if the HID interface class were not protected, you still wouldn't be able to claim it because the USB HID interface is already claimed by the system's generic HID driver. The generic HID driver exposes a non-exclusive "raw" HID interface to applications. WebHID uses this non-exclusive interface which is why it doesn't have the same limitation as WebUSB.

FWIW Mozilla updated their position on Web Serial API to "neutral" and clarified that they might be okay with enabling the API with an add-on.

https://mozilla.github.io/standards-positions/#webserial

Allowing serial but not HID would be really strange. With HID you get standard identifiers that let you filter out devices that are too dangerous for the web. With serial you get nothing. Even if you know a device is dangerous, there's no way to protect users from it.

The site has to request permission to access a device, then the user has to select the device from a permission dialog to grant access.
Re:Google Abandons Web Environment Integrity API on Friday November 03, 2023 @07:06PM (#38136239)
That's the wrong comparison. We used to only have dedicated POS systems, now we have the option to run POS software on a general purpose computing device. The question is why should that POS software be a native app instead of a web app?
Re:Good bye, Helium... on Friday April 02, 2010 @05:58PM (#1237691)
Who says oil can't be produced? I mean, it doesn't make sense to use it as a fuel source since you'd have to put in at least as much energy as you'd be getting back out, but you can still produce it.
Re:Woobius introduces: the Eye on Friday March 05, 2010 @05:57PM (#1170716)
There are plenty of standalone apps for videoconferencing. I don't think there's any need to package it with a whiteboard app unless you can come up with an innovative way to integrate the video with the whiteboard (indexing video frames to scribbles, maybe?)

In my experience, having a video feed is pretty much worthless for productivity; if anything, it's distracting. Much more useful is having voice chat and the ability to share files seamlessly. Again, these are needs that can be adequately fulfilled by Google Docs, Google Talk, Skype, etc, so there's no reason to reinvent the wheel.