I agree with the premise that selfhosting is not something the layman can or want to do, but the assumption that self-hosters only host software that serve themselves is very, very dumb, and clearly comes from the mouth of someone who self-hosts out of hate for corporate services (same, though) and not for the love of selfhosting.

He complains that the software he uses can’t handle multi-users, but that sounds like a skill issue to me. His solution is to make his government give him metered cloud services. What he actually wants is software that allows multi-users. What he wants, by extension, is federated services.

The bulk of users on the fediverse are on large, centrally/cloud hosted instances, but the vast majority of instances are self-hosted, and can talk to the centrally hosted instances, serving usually more than the 1 user who’s hosting the instance in their attic.

The author conflates self-hosting with self-reliance, and I understand why, but it’s wrong. If you’re part of this community, you’re probably not some off-gridder who wants nothing to do with society, self-isolating your way out of the problems we face. If you’re reading this, you already know that we don’t have to live on our own individual and isolated paradise islands to escape Big Tech. Federation is the future, but selfhosting is fundamental to that, and not everything can or should be federated. Selfhosting is also the future.

Lol. So we trust local governments and communities now?

Has anyone ever worked with them IT wise?

I do so in four different EU countries and know people who do in the US and Canada. And…well…there is a reason local governments often went towards the cloud services. Do people think Joe Admin in Bumfucknowhere can operate what basically becomes a MiniDC? And who controls that?

Sorry. Either go “host at home” and only fuck up things for oneself. Or do it properly with a proper DC. Colocate if you want. But that? I know it sounds appealing, especially for someone entering selfhosting (like the author did a few weeks ago). But there is a reason hosting is a business once it comes to other peoples data.

End-to-end encryption means the service provider can’t see your data even if they wanted to

Not necessarily. All it means is that intermediaries can’t see the data in transit. You need to trust that the data is handled properly at either end, and most service providers also make the apps that you run at either end. Your library is more likely to buy whatever is cheapest than what respects your privacy the most (e.g. probably Google drive, not Tuta or Proton).

The incentives for even community-hosted services (e.g. if the library spun up its own cloud servers) to share/sell information is just too high. Maybe the library found someone uploading illegal content, and they wanted some monitoring in there to catch service abusers going forward. They’ll probably put something into the client that a third party monitors, and now you have someone snooping on everything.

Instead of this, I think P2P storage is the better option for those who don’t want to self-host. That way there’s an incentive for the person providing storage to not know what it is (reduce liability), as well as the person submitting the data (reduce risk). Unfortunately, most current solutions here are a little shady, because they either rely on volunteers (no guarantees about data integrity) or anonymous payments (again, no guarantees about data integrity).

I’d like to see something in the middle:

• apps that work off buckets of data, that the user configures
• services that provide data guarantees that users can choose (e.g. AWS S3, Backblaze B2, Hetzner Storage boxes)
• common protocol between apps for accessing this data

So if you want more storage, you buy said storage and know who is responsible for protecting it, and your app doesn’t care where it comes from.

That’s possible, but the bigger leap is getting people off the major platforms like Google’s or Microsoft’s cloud.