So I recently got an excuse rant about my opinions on federated tech. I think it's pretty much the best we can hope for in terms of liberating tech, with very few niches where fully distributed tech is preferable.
Needing a server places users under the power of the server administrator. Why do we bother? "No gods, no masters, no admins!' I hear you shout. Well, there's a couple reasons...
Maybe using software is just an intrinsically centralized activity. One or a few people design and code it, and an unlimited number of people can digitally replicate and use it. Sure, it may be free software that everyone can inspect and modify... but how many people will really bother? (Nevermind that most people don't even have the skills necessary.)
Okay, so we always kind of rely on a central-ish dev team when we use tech. Why rely on admins on top of that? I believe the vast vast majority of people doesn't have the skills and time to operate a truly independent node of a fully distributed tech. Let's take Jami as an example:
"With the default name server (ns.jami.net), the usernames are registered on an Ethereum blockchain."
So a feature of Jami is (for most users) implemented as a centralized service. Yikes. You could build and run your own name server (with less embarrassing tech choices hopefully), but who will really bother?
But say you bothered, wouldn't it be nice if your friends could use that name server too, and gain a little independence? That sounds a lot like decentralized/federated tech.
Keeping a decent service online is a pain in the butt. Installing SW updates, managing backups, paying for hardware and name services... nevermind just the general bothering to understand all that mess. And moderation, don't forget moderation. I'm saying it's not for everyone (and we should appreciate the fuck out of [local admin]).
I believe that servers and admins are our best bet for actual non-centralized tech. A tech-literate person tending a service for a small- to medium-size community is much more feasible than every person running their independent node (which will probably still depend on something centralized).
And maybe that's just the way we bring good ol' division of labour to the Internet. You have your shoemaker, your baker, your social media admin. A respectable and useful position in society. And they lived happily ever after.
There are plenty of community managed lists that are kept up for various things, with multiple sources of truth to choose from. As an example, adblockers do it. You can manually adjust as necessary, and the provider has a list, but there are also plenty of other blacklists /whitelists you can use in addition to or in place of theirs.
While I don't think serverless is necessary, I think genuinely P2P services are possible using similar approaches. The "primary" developer can provide and maintain default lists for moderation, but any other source can provide their own, moderated or curated to different standards. You make the default distribution automatically subscribe to reasonable defaults, other distributions can do their own, and end users can adjust as desired.
If you allow these white/blacklists to keep you from storing/redistributing content as well, the worst concerns of bad actors abusing your network to do genuinely fucked up shit are reasonably mitigated.