5 ms·

> The spec is still in draft because Apple refuses to let it move forward This is untrue. Web standards need two independent implementations. Google can’t conv

> The spec is still in draft because Apple refuses to let it move forward This is untrue. Web standards need two independent implementations. Google can’t convince any other rendering engine besides their own to implement it. It doesn't take a single no from Apple to veto it; it takes a single yes from anybody outside of Blink to move it forward. Nobody is doing that. Here is what Mozilla have to say about WebUSB: > Because many USB devices are not designed to handle potentially-malicious interactions over the USB protocols and because those devices can have significant effects on the computer they're connected to, we believe that the security risks of exposing USB devices to the Web are too broad to risk exposing users to them or to explain properly to end users to obtain meaningful informed consent. It also poses risks that sites could use USB device identity or data stored on USB devices as tracking identifiers. — https://mozilla.github.io/standards-positions/#webusb https://mozilla.github.io/standards-positions/#webusb Until Google can convince anybody outside of Blink to implement it, it is not a standard it’s a Blink-only API.

leptons 6mo ago
Apple has provided no alternative, and no suggestions for how to improve the draft. They are not helping advance the draft only for selfish reasons. They also won't allow any other browser on iOS for the same selfish reasons. Apple continues to use abusive business tactics, and it's why they are being sued by the DOJ in an antitrust lawsuit. Them not implementing and not even suggesting changes to WebUSB and WebBluetooth are just further examples of it. https://www.justice.gov/archives/opa/media/1344546/dl?inline https://www.justice.gov/archives/opa/media/1344546/dl?inline >Because many USB devices are not designed to handle potentially-malicious interactions over the USB protocols and because those devices can have significant effects on the computer they're connected to So the alternative is installing questionable drivers from questionable websites that give an attacker full-access to the entire computer. This is far less good for security, and is unfortunately the norm right now. >we believe that the security risks of exposing USB devices to the Web are too broad to risk exposing users to them or to explain properly to end users to obtain meaningful informed consent. So is every other browser API that's currently implemented that requires explicit approval from a user. It's nonsense to single out WebUSB specifically. > It also poses risks that sites could use USB device identity or data stored on USB devices as tracking identifiers. Bullshit. You have to explicitly allow WebUSB to interact with any website that requests it. It does NOT allow arbitrary tracking, and this sentence proves that whatever Mozilla writes about it is disingenuous, trying to incite hysteria about an API.
- bcjdjsndon 6mo ago
  > So the alternative is installing questionable drivers from questionable websites that give an attacker full-access to the entire computer. This is far less good for security, and is unfortunately the norm right now WebUSB isn't a driver, it relies on underlying usb drivers. What is the need here for a webpage that also needs to access specific hardware not exposed generically?
  - leptons 6mo ago
    >WebUSB isn't a driver, it relies on underlying usb drivers. I never said WebUSB "was a driver". But it does not rely on specific usb device drivers being installed for specific devices. >What is the need here for a webpage that also needs to access specific hardware not exposed generically? There are already plenty. You don't need to ask me because you'll likely just shit on what I write, so here's a list compiled by someone else: https://github.com/webusb/awesome https://github.com/webusb/awesome That just scratches the surface. I'm more interested in WebBluetooth, which Apple is also blocking from standardization. I manufacture a bluetooth enabled device that I'd like to have a simple web application to interface with, rather than needing to pay Apple for the privledge to develop an app for their app store, where they can then extort me for $$$ for any sales made through the app. It's no different for WebUSB, it has many, many uses, but Apple is choosing profit over progress.
    - bcjdjsndon 6mo ago
      It's just not a driver though mate I dont know how I could make that clearer
- JimDabell 6mo ago
  You’re avoiding my point. What you said: > The spec is still in draft because Apple refuses to let it move forward …is simply untrue. Apple cannot stop it from being a standard by refusing to implement it. As long as anybody else is willing to produce a second implementation it can be a standard. The thing that is preventing it from being a standard is that nobody is willing to do this. If Apple did not even exist then WebUSB would be no closer at all to being a standard.

leptons 6mo ago

Apple has provided no alternative, and no suggestions for how to improve the draft. They are not helping advance the draft only for selfish reasons. They also won't allow any other browser on iOS for the same selfish reasons. Apple continues to use abusive business tactics, and it's why they are being sued by the DOJ in an antitrust lawsuit. Them not implementing and not even suggesting changes to WebUSB and WebBluetooth are just further examples of it. https://www.justice.gov/archives/opa/media/1344546/dl?inline https://www.justice.gov/archives/opa/media/1344546/dl?inline >Because many USB devices are not designed to handle potentially-malicious interactions over the USB protocols and because those devices can have significant effects on the computer they're connected to So the alternative is installing questionable drivers from questionable websites that give an attacker full-access to the entire computer. This is far less good for security, and is unfortunately the norm right now. >we believe that the security risks of exposing USB devices to the Web are too broad to risk exposing users to them or to explain properly to end users to obtain meaningful informed consent. So is every other browser API that's currently implemented that requires explicit approval from a user. It's nonsense to single out WebUSB specifically. > It also poses risks that sites could use USB device identity or data stored on USB devices as tracking identifiers. Bullshit. You have to explicitly allow WebUSB to interact with any website that requests it. It does NOT allow arbitrary tracking, and this sentence proves that whatever Mozilla writes about it is disingenuous, trying to incite hysteria about an API.

bcjdjsndon 6mo ago
> So the alternative is installing questionable drivers from questionable websites that give an attacker full-access to the entire computer. This is far less good for security, and is unfortunately the norm right now WebUSB isn't a driver, it relies on underlying usb drivers. What is the need here for a webpage that also needs to access specific hardware not exposed generically?
- leptons 6mo ago
  >WebUSB isn't a driver, it relies on underlying usb drivers. I never said WebUSB "was a driver". But it does not rely on specific usb device drivers being installed for specific devices. >What is the need here for a webpage that also needs to access specific hardware not exposed generically? There are already plenty. You don't need to ask me because you'll likely just shit on what I write, so here's a list compiled by someone else: https://github.com/webusb/awesome https://github.com/webusb/awesome That just scratches the surface. I'm more interested in WebBluetooth, which Apple is also blocking from standardization. I manufacture a bluetooth enabled device that I'd like to have a simple web application to interface with, rather than needing to pay Apple for the privledge to develop an app for their app store, where they can then extort me for $$$ for any sales made through the app. It's no different for WebUSB, it has many, many uses, but Apple is choosing profit over progress.
  - bcjdjsndon 6mo ago
    It's just not a driver though mate I dont know how I could make that clearer
JimDabell 6mo ago
You’re avoiding my point. What you said: > The spec is still in draft because Apple refuses to let it move forward …is simply untrue. Apple cannot stop it from being a standard by refusing to implement it. As long as anybody else is willing to produce a second implementation it can be a standard. The thing that is preventing it from being a standard is that nobody is willing to do this. If Apple did not even exist then WebUSB would be no closer at all to being a standard.