If you're just getting started on here, you may be wondering why this place has so many servers and apps. Why make it so complicated?

Click here to find out why:

➡️ https://fedi.tips/mastodon-and-the-fediverse-beginners-start-here/#whyisthefediverseonsomanyseparateservers

Twitter is all on one server (twitter.com). This made it VERY easy for Musk to buy it. Any centralised network can be bought out just like this.

The Fediverse is different: as long as we stay spread out on many servers, no one will ever be able to buy this network, not even the richest person in the world.

Mastodon and the Fediverse: Beginners Start Here | Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse

@feditips In the long run, Mastodon really needs (1) A front end that enables new users to identify interests then signs them up to the relevant server behind the scenes; (2) Replace developer-centric "Home", "Local", "Federated" with labels that are clear to users; (3) mandate warning time before a server is taken down and provide one-click way to migrate to new server.
@Corb_The_Lesser @feditips the issue is that there is no central authority figure to push any of this really. No one controls who can start a server or what warnings they need to abide by. And there's no real central authority to determine who's server you go to. That lack of centralization has 'drawbacks' but I think the trade-off is worth it.
@Corb_The_Lesser @feditips seeing as the basis for the fediverse and mastodon as a whole is essentially the same as email. multiple providers all communicating within the same protocol, there really doesn't need to be an "easy to identify server of interest", since none of us are a sole niche, having a niche centric server is counter-intuitive, and in the end, it doesn't even matter.
home, local, federated is pretty obvious isn't it? it's the same as twitter with one service channel
@Corb_The_Lesser @feditips there's no authority that could mandate an advance warning. And there are plenty of things that could bring an instance offline without warning like the owner dying and their server crashing without someone to maintain it, a datacenter catching fire, etc