Hacker News Reader

First you need an Operating System that can withstand direct Internet exposure for a decade without incident. Any administration required is going to kill it dead. There are no suitable OS options available at present.

Then you need to make the actual service dead simple to use from anywhere. Punching through NAT and firewalls are the main issues there.

View on HN

An immutable linux base, like Flatcar, combined with dockerized apps for isolation and easy per-container updates could come pretty close if some engineering were put into UX.

You'd need to have unattended upgrades, or perhaps a companion app where you can send the user a push notification to say "hey bruh update your shit". Would also need engineers to support those updates.

Tailscale pretty much solved NAT traversal.

The containerizing is almost a capability based security system. Instead of adding that layer to block everything except a certain resource, why not change the defaults in the OS so that it defaults to NO access instead? Saves resources, provides much better security.

Reply on news.ycombinator.com