Maybe? Looks to me though like the increasing centralisation around mastodon the brand and platform which eventually rubs against the decentralised “admins relying on community management and donations” nature of the rest of the Fedi.
Should admins feel left behind or unheeded by the platform devs but also feel compelled to rely on mastodon the platform, moments like this, like the default mastodon.social in the app, will look like underestimated mistakes.
@maegul Well, mastodon.social becoming the default server for Mastodon was the big reason I started work on Firefish last year.
And what did I learn from that experience? That even small Fediverse projects draw outrage if they gain a little bit of notice. There were other problems but that was also a big one.
This is partially why I’m building akkomane.social slowly. The moment you start a server, you’re taking on a little bit of risk. The best thing you can do is test and build incrementally.
@atomicpoet which is why I can’t help but question the efforts of all the people working on platform diversity. It’s not easy and the software is just the beginning. Masto have, AFAICT, aren’t their spot, even if just with consistency over time.
Meanwhile there are many disparate alternatives around. If they all care about diversity, they’d be better banding together into organisations more resilient against the tribulations of running a popular platform.
@maegul The problem isn’t platform diversity. The problem is an HOA that does everything in its power to preserve the status quo.
For a good long time, their shenanigans worked. But now that actual big entities and influential people are involved, they’re fast finding out that they no longer can enforce the status quo.
What’s funny is that most of the HOA uses Mastodon servers. They still federate with mastodon.social. For all the talk about forking Mastodon, it is highly unlikely they’ll do – they’re certainly not contributing to any forks right now even though they keep complaining about Mastodon.
Add comment