Hey... that just gave me a small idea... what if we made a "flock" or "herd" of Mastodon servers? The group of servers would all federate with each other, have the same block and allow lists, moderation policy and teams spread throughout them.
When you make an account you can be assigned a random instance name within the flock. If your instance goes down you could still possibly log in using other servers? Main benefit would be spreading server costs and maintenance effort and de-centralized operating, but still keep a centralized feel to it?
Honestly that’s probably the best sort of solution. A group that has some minimum standards of moderation and maintenance/upgrade management plan and just evenly distribute the load as people arrive.
Then as a second phase make it easy to transfer, that way at the point the user gets comfortable they can easily swap to a better* “home” for those that care, for those that don’t, make the server choice be virtually invisible.
I’m guessing you meant this sarcastically, but you may have been right for the wrong reasons. Look at this graph, by the metric of the way the fediverse works that is a failure. Apple and Google are massively dominant because people don’t want to think about it and most just go with their phone os maker who makes them create one when setting it up, and there is no fediverse server equivalent to that.
Nevertheless email stays the defacto standard for business communication and has stayed intercompatible with a wide range of clients, servers and plugins. So this graph could be better but is apparently not a big issue as long as companies and unis keep running their own servers, forcing big tech to stay with the standards.
I mean, I hear you (we’re both here after all), but honestly, I think this is a bad take and approach (if getting more users is a goal.
It’s not the 90s anymore. And even email services are given to you by your employer or selected from the closest big brand provider (Google etc).
All of which is a far cry from “nerdygardeners.io” administered by some rando anonymous account you’ve never heard of before.
For mainstream success, the instances thing was dead on arrival. Just was and is. Which is fine, the Fedi can be and arguably should be something else.
IMO the success of BlueSky is good for the Fedi. It can take the “let’s be the next mainstream thing” monkey off of its back and just be itself.
Not really. I mean, sure it’s the same concept, but email has been getting semi-centralized between the big players now, with gmail and maybe icloud getting the largest chunk of users. That would be similar to letting users choose between .world or .ml to sign up with, which is against the fediverse principle to spread the load as wide as possible.
When you present the lowest common denominator internet user with hundreds of instances to choose from and requiring them to think further than clicking through a sign-up page, you lose user interest pretty quickly.
The idea would be the servers would have shared ban/block lists and similar rules so that they can share the load of having open sign ups.
Basically a coop of instances to improve on-boarding. If you join the coop then you get added to the pool of instances that get assigned normies at random.
If the authentication was federated it’d be ideal as well but I assume this would be outside the scope of AP and would cause issues if you tried to post from your mastodon.social account from mastodon.world’s server for instance.
See my reply to u/Rentlar, but for most users, yes, the easier the onboarding, the more accessible it is; the more people won’t immediately run away because they’re afraid they’ll make the wrong choice.
Or you make it like a traditional website with an API used by people making frontends, but the backend (the database) is decentralized, just like regular websites but instead of having a bunch of servers owned by AWS it's just a bunch of people providing storage space on their servers.
What is the incentive for people to host an instance at the moment?
What is the incentive for people to share files via peer to peer networks?
What is the incentive for people to host Minecraft servers?
Need me to go on?
If in your mind the only incentive that people have to host instances is to have power over it and its users then they're exactly the kind of people you don't want to see hosting instances.
Well, in a system like I'm talking about, adding your server and storage space in the mix would make the whole thing more reliable and add to the storage capacity so more content can be hosted/backed up, just like paying for a second server to host a website allows to store more stuff and to start creating backups. You would still help build the community (the website), you just wouldn't have an administrative role outside of the communities you would want to moderate.
Just log onto mastodon.social and be done with it. That's the one that will still be running until the they turn out the lights on the service, I figure. And then go kick in a buck or two a month on Patreon to help defray development and server costs. (Not being the product is worth a donation by itself, I figure.)