planish

Why would they design around evaporative cooling when water consumption is a problem?

Is it filled with the type of people that one might wish major governments could stop, though?

ZeroNet

What's up on ZeroNet these days?

Capitalism runs on top of government. Governments create and enforce the notion that a human, or a fictional human with fractional ownership (corporation), can in turn own arbitrarily large and important objects.

This is often done at the behest of said arbitrarily-large-and-important-thing-owners, who also come up with other similarly terrible ideas to have the government do.

Probably not any existing systems; you can still finger and thus demand censorship from a block producer, and you end up with situations where you just can't host the chain anymore because it's full of pirated MP3s or whatever now.

And they introduce new problems around having to globally replicate everything and thus getting the net performance out of the system that you get from the worst server involved.

If you need to track some kind of root signing key for a whole p2p system, or something, maybe you can stuff it into Ethereum somewhere. But I don't think you can get very far trying to actually run a service out of a globally replicated database, and even then you'd have hundreds of operators in legal trouble rather than no operator.

Something like Tor only solves half the problem. A Tor hidden service still has physical reality and a person who is hosting it, and who can be held responsible for failing to register the thing with the feds or file a moderation transparency report or whatever the latest nonsense is. The anonymity network helps to hide where the equipment and who the operator is, but there's still a single point of failure and a person to blame for the community.

We need a way to run online communities that are not online services: no single point of failure, no individual or partnership describable as a service's operator, and no meaningful way in which one person provides access to the system to another person.

You may be looking for The Promised LAN.

How did that happen?

Yeah, a TPM is, essentially, a piece of bondage gear. It's shackles put on you to try and convince someone else of what you can't do. It has niche applications but it's not a valid thing to require of the general population.

Computers have systems (BIOS, EFI, ACPI) that give the people who make the machine responsibility for providing a standard, publicly-defined way for the OS to enumerate the hardware, and to use the hardware in a basic way even if the OS has never heard of it. Linux can get a kernel panic on the screen even if it has no idea what your GPU is, because EFI understands it and Linux understands EFI. It is set up this way partly because there's a real possibility of hardware being added or removed, partly because people routinely mix and match parts, and partly because IBM mistakenly designed a good system that was easy to work in and not one that kept them in business.

Phones (and phone-derived systems like the Raspberry Pi and other single-board computers) don't implement a standard. The hardware and its boot process assumes tight integration between the hardware and the software, usually to the point where the bootloader refuses to load anything not signed by the device manufacturer, unless it is satisfied that it has been given that manufacturer's permission to be unlocked. (Computer secure boot implementations generally trust, for example, Microsoft, as well as the machine owner, who can load their own keys.)

Instead of the CPU developers releasing example EFI implementations, they release forks of the Linux kernel that they maintain as long as that chip is the latest chip they sell, and then fork off the mainline kernel again for their next chip. And the device makers ship devices by starting with the chip maker's kernel, customizing it for the device, giving it a "device tree" that tells it everything that is supposed to be in that particular device, and shipping it. For a few years they port patches from the current kernel onto this forked kernel, and then they stop. With no standard to develop software against, and no documentation for what's in a device and how to use it like there is for the standard's interfaces, the only practical way to run software on a device is to start with that patched kernel.

Mainline Linux refuses to adopt and maintain the chip and device makers' low-quality, chip-and-board-specific kernel changes (often because they break the kernel for other uses), so you can't generally use a mainline Linux kernel instead. If you tried to tease out and improve the device-specific patches to the point where mainline Linux would take them, the device would be hopelessly outdated by the time you were done and you would have dozens of job offers to occupy your time as a highly skilled embedded Linux developer. The work is not practical given the tiny number of people who would benefit from it for a particular device, and how little it pays off compared to just buying a new device with a more up to date forked kernel available.

"Maintaining" a device for LineageOS or other open software eventually collapses under the weight of mainline Linux's changes and the necessary chip and device maker patches no longer being practically reconcileable.

I don't think this is going to change the overall situation, it's just a single point new system requirement, like the plausible GPU was for Vista.

Now, if they start expiring the old TPMs every few years, and Windows 12 needs a TPM 4.0 or something, then this will change the overall situation. At least on the Windows side.

“hanging with the bad crow"

That's my favorite Sonic mission.