News for hackers. Stuff that matters.

A comment on Direct Sockets API in Chrome 131.

Re:Direct Sockets API in Chrome 131 by tjoff on Saturday November 02, 2024 @03:33AM (#42024676)
Great, so now a mis-click and your browser will have a field day infecting your printer, coffee machine and all the other crap that was previously shielded by NAT and/or a firewall.
[ Parent | on HN ]
Re:Direct Sockets API in Chrome 131 by jeroenhd on Saturday November 02, 2024 @04:54AM (#42025009)
As long as they don't change the spec, this will only be available to special locally installed apps in enterprise ChromeOS environments. I don't think their latest weird app format is going to make it to other browsers, so this will remain one of those weird Chrome only APIs that nobody uses.
[ Parent | on HN ]
Re:Direct Sockets API in Chrome 131 by fensgrim on Saturday November 02, 2024 @08:10AM (#42025900)
> special locally installed apps in enterprise ChromeOS environments

There was https://developer.chrome.com/docs/apps/overview though, so this seems to be a kind of planned feature creep after deprecating former one? "Yeah our enterprise partners now totally need this, you see, no reasoning needed"

[ Parent | on HN ]