| Enshittification is caused by the lack of secure general purpose computing, and will continue until we get it back. We had it back in the 1980s, when we booted from write protectable floppy disks, and could easily verify backups. What nobody realized at the time was that was a capability based security system. Very coarsely grained, but you couldn't accidentally fubar everything. It was easy to know what was being risked at any given time. We used "shareware" disks, typed in things from magazines, and generally could run ANYTHING, in almost perfect safety. We always had our known good boot disks, and their backups, and our multiple copies of our data. Until we can run any old random executable, we're going to avoid "untrusted" sites, and stick to the walled gardens our friends hang out at. Capabilities based systems like Genode might be able to get us there. VMs and Containers were a make-do / very crude version of capabilities... you specified what disks a virtual machine could access, thus it was better than nothing. WASM is the latest attempt down this road, and I only hope they don't "improve" it by destroying the capabilities model it provides. What's really sad is that this was all solved back in the 1970s, and it's only the accident of history that we don't have capabilities based systems available that a normal person could use. In response to the need for a single computer to handle multiple levels of classification due to the needs of the Air Force in the Viet Nam conflict, research was done, and solutions were found. --- Think of the difference between handing someone $5, or your credit card.... which is safer? You can only lose $5 in the first case. That is capability based security. PS: Sorry, I write defensively because of the way replies tend to work here on HN. |
that's a very interesting idea.