by greyface-
5 subcomments
- Mozilla's response to "Request for Mozilla Position on an Emerging Web Specification", June 2020:
> For raw device access as envisioned in a number of APIs (Web USB, Web Bluetooth, Web NFC, and Web MIDI), the risks of exposing those APIs to users cannot be reasonably conveyed. This is pretty much an intractable flaw of allowing raw, non-semantic access to devices regardless of the protocol used to do so.
> The specific issue is: it's not intuitive that allowing malicious-site.com to access your Bluetooth keyboard might give that site access to your stored passwords, give them the ability to hijack your DNS settings, or allow them to encrypt your hard drive and hold it ransom. And if it's not immediately obvious how those things are possible, that only serves to demonstrate how completely non-intuitive the risks are and how intractable trying to explain them in a permission prompt would be.
https://github.com/mozilla/standards-positions/issues/95#iss...
by geekuillaume
4 subcomments
- WebSerial was just introduced in Firefox 151. It was already available for 5 years in Chromium based browser. It's so new in Firefox that even caniuse is not up-to-date: https://caniuse.com/web-serial.
- Using serial comms from the browser is really important in educational robotics programs. Both First and Vex platforms support it. Kids can access the web based coding environment on their chromebooks, and send code to the robots with a usb cable.
We recently restarted our middle school robotics club. The school had a lot of old Vex EDR equipment for which the coding software is windows only so that really limited what we could do related to coding. Glad to see Firefox getting up to speed on this.
- Great to see Firefox getting on board. I wrote an alternative to Arduino's serial plotter that works in Chrome. Hopefully it's not too hard to get Firefox working too? Patches welcome:
https://github.com/skybrian/serialviz
- Woah this is a MASSIVE deviation from FF's previous philosophy on allowing WebSerial. This is a GOOD thing!
- WebSerial in Firefox?! Finally! One of the very few things I use chrome for.
- On iOS the page promotes the App Store version of Firefox, which is based on WebKit and doesn’t support Web Serial.
by trainyperson
0 subcomment
- I used WebSerial + WebSockets during hardware to prototype some connected hardware (on boards that didn’t have WiFi).
Plug in to USB, fire up the web app, and then press a button in NY to light up LEDs in SF – it was exciting stuff!
I never tried actually programming the boards over WebSerial; that obviously opens up many more use cases. I’m thinking about the success that p5.js has had in the creative coding community, largely driven (I think) by a low barrier to entry since it just requires a web browser to get started.
by singiamtel
2 subcomments
- Amazing feature for beginners. Is it possible to do this using Arduino?
by monegator
3 subcomments
- what the fuck since when they are allowing webserial / webusb?
I've always agreed with the reservations about browsers being able to control peripherals. I'd rather download a python script i can inspect.
by psychoslave
1 subcomments
- So, what's adafruit? Related to Adam programming language?
- As long as you can download the environment for offline use.
by nathanmills
0 subcomment
- WebUSB next? I would like to be able to configure my keyboard but it can only be done via their website which requires WebUSB.
- Why not from a firefox running in a virtual machine inside firefox ?
RAM is cheap now. /s
- [dead]
by Insimwytim
0 subcomment
- The design of this webpage is horrendous.
- Old shit is shit
- Feels a bit out of place that the website tries to aggressively make me download Firefox, with multiple links on the site for it. Like it's the 2000's again and I'd need ActiveX or something. But it's to use a standard.
Sure, the standard is cool, have used it to flash Meshtastic to some LoRa boards, before advancing to use VS Code + ESP-IDF to flash in my own LoRa code.
- That's a start at improving something. But it won't rid itself of the Playskool/Fisher-Price gimmick factor or have any lasting effect until we can convince JS developers to write their own tools in a standards-compliant dialect and use standardized APIs so that contributors can use the runtime they already have installed instead of being cajoled and browbeaten into installing NodeJS or Bun or Deno or whatever to do what the browser runtime is perfectly capable of: opening a project directory, executing the code comprising the build script, and outputting the build artifacts when it's done.
Hacker News