[ta1243]

Those sorts of things just need to boot to a web browser in full screen with some watchdog software in the background, launching from a read only disk (or network image). Get a problem, just unplug it and plug it back in. Make it POE based so you can easily do it automatically, stick them on a couple of distros (maybe even half on bsd, half on linux, half using chrome, half on firefox)

[polski-g]

A web browser is an unbelievably complex piece of software. So complex that there are now only two. And also so complex that there are weekly updates because there's so many security holes.

[autoexec]

> So complex that there are now only two

There are more than two, and the vast majority of the time people don't need anywhere near the complexity that modern browsers have shoved into them. A lean browser that supported only a bare minimum of features would go a long way to reducing attack surface. As it is now, I already find myself disabling more and more functionality from my browsers (service workers, WebRTC, JS, SVG, webgl, PDF readers, prefetch, mathml, etc)

[echoangle]

There are more than 2 browsers, but only 2 rendering engines, which are the complicated part of the browser.

[autoexec]

More than two there too. For example: WebKit, Blink, Gecko, LibWeb, Servo, Goanna, Presto, and Libwww or whatever Lynx is using these days.

[echoangle]

You’re right, I completely forgot WebKit. I would say there are currently 3 competitive engines, the rest are not very popular.

[Osiris]

The first three cover basically 99% of browsers.

[autoexec]

Yeah, options exist but it's not a very diverse ecosystem in practice. I'm excited and optimistic about ladybird for that reason. We need more options.

[ta1243]

When accessing a closed departure board display then that isn't a problem