The people who don’t want you to run your own servers are the ones who want to run the servers.

People will happily run their own servers if it’s so simple to do that they don’t even know they’re doing it.

You want people to run their own servers? Design and build servers for individuals, not communities and let communities arise from the interconnections between those servers.


Because that’s the only way we can compete on ease of use with centralised systems. Not by mimicking their complexity but by side-stepping it. There is orders of magnitude difference in complexity between a system designed to serve just one and one designed to serve one, two, or a hundred thousand.

Centralisation thrives on complexity; decentralisation on simplicity.

@aral does it though? This may be unfair of me (I’m all for decentralisation BTW) bit when I was running IndieWeb functions on my blog, it was ridiculously complicated.

When I tried Micro.Blog, it was convoluted and awkward. was the same, albeit less so.

I hope it will get there some day, but my experience is the opposite. Centralisation is simple (sign up for Twitter, post your memes), and decentralisation is complicated unfortunately. 😕

@kev @aral I think the crucial word is "thrives". What you're saying is an example of how I read Aral's point.

When tools, protocols, or activities become too complicated, centralization will creep in. Hosting is complicated, and lo and behold we end up with largely centralized Web.

It's on us to design our tools such that they are *simple*. And when we do, centralized services will have less room to manoeuvre. The point is: we should not parrot centralized services, but instead design simpler tools.

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.