Live data from Hacker News

Show HN: I built an HTML5 RTL-SDR application

radio.ea1iti.es

21–30 of 62 posts

Re: Show HN: I built an HTML5 RTL-SDR application

#21
I'm unable to get it to work with my receiver (setRegBuffer failed block=0x600 reg=74, Caused By: RadioError.UsbTransferError: USB write failed value=0x74 index=0x610 status=stall), but I love the idea!

Looking forward to a local webusb+rtlsdr based Flightradar.

Re: Show HN: I built an HTML5 RTL-SDR application

#23
post #14

` ` let's get that in html6! Nice use of web components!

HTML is a living standard. There likely won't ever be a "html6". https://html.spec.whatwg.org/multipage/introduction.html#his...

It's a living standard for today, but no one knows what tomorrow brings

Re: Show HN: I built an HTML5 RTL-SDR application

#24

Earlier quoted context omitted.

HTML is a living standard. There likely won't ever be a "html6". https://html.spec.whatwg.org/multipage/introduction.html#his...

It's a living standard for today, but no one knows what tomorrow brings

Yeah, that is why I said likely.

Re: Show HN: I built an HTML5 RTL-SDR application

#25
post #14

` ` let's get that in html6! Nice use of web components!

HTML is a living standard. There likely won't ever be a "html6". https://html.spec.whatwg.org/multipage/introduction.html#his...

Exactly. And there is no HTML5, either.

Re: Show HN: I built an HTML5 RTL-SDR application

#26

Earlier quoted context omitted.

Yeah... It's an accident waiting to happen with someone's security key. (Yes, I'm aware chrome tries to protect that one... for now) We really need more intentionality around hardware use. There's many SDR apps already packaged for all systems. Stop trying to juggle chainsaws, please!

The UI makes it very obvious as you have to select a device. Anyone who is worried, including corporations, can disable it.

The UI also very temptingly looks like all the website can do is use the device for its intended function, because that's how normal users think and how it should work. But most devices were built with an assumption of trust between the driver and hardware, and now suddenly there's a security boundary there. With this there's an untrusted agent interacting with a device that may have vulnerabilities, which can itself then also interact with vulnerabilities the host may have towards USB devices.

It's not that this can't be done, it's that this is changing the rules that existing security is built on.

I would try to make it work with whitelists and/or restricting the functionality to browser add-ons rather than plain websites. Both add extra checkpoints where some security can be added back in, or rather perform this "weakening" of the previous security boundary in a more controlled manner.

Re: Show HN: I built an HTML5 RTL-SDR application

#29
post #17

Earlier quoted context omitted.

Yes, but so is Chrome and many other browsers.

You shouldn't treat them as different brosers. They're just skins.

Chrome-only is not correct either and that's what Chrome API sounds like

Re: Show HN: I built an HTML5 RTL-SDR application

#30
post #16

I wish Firefox would implement this API too, it's been years.

Mozilla's position is to not implement this API due to security and privacy concerns, and I agree with them on that even though I'd really like to use this API too.

Given that it's been available in Chrome for 7 years, if there were any security and privacy concerns we should be able to point to at least one abuse of this API right?
Post reply on HN