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.
@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. Write.as 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. 😕
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.
As a friend put it: at least sometimes we have to be able to say "this code is now complete". No new features needed.
@kev @aral I believe the point is technical complexity. Software that is more complex tends to centralize over time (think email or maybe Matrix), while software that is simpler can easily be decentralized since more people can actually set it up (such as possibly web servers or IRC).
We need to make hosting servers simpler if we want more people to do it without being sysadmins.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.