joinmastodon.org (the ‘official’ way to get join mastodon), has a default server for its join button. To me this looks very similar to the default server that appears when you try to create a bluesky account. So… I guess that’s not a barrier after all.
It was revolutionary, the utter example of a “killer app” that had people and businesses running out to buy computers just to replace paper memos. You setup your mail server to hook into that brand new, stunning ecosystem of near instant communication from across the world.
Now there are 6,000,000,000 “killer” apps you can install in seconds from your pocket computer. I can hit “install” and be talking face to face with a stranger in Singapore in 30 seconds, all from easy, low effort walled gardens.
Federation was and is a reasonable way to host things, but comparing current systems to email is a misnomer. People dealt with federation because they had to. If gmail has existed in 1983, no one would have had their own federated email servers. Hell, AOL tried to choke the internet itself to death and almost succeeded in the early 90s because it was an “all in one” solution. They had aol only webpages and everything, including email. Its a twist of fate that they failed, mainly due to the onset of always on broadband, not because people didn’t want things easy.
Make things easy, people will use it. They will only do hard if they have to.
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?
If they have the same people running all of them, how is that different from running a single mastodon server in kubernetes, so that it doesn’t get overloaded?
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.
As long as the fediverse has a barrier to entry for most people of mandating choosing a server first, it will never become the mainstream choice.
joinmastodon.org (the ‘official’ way to get join mastodon), has a default server for its join button. To me this looks very similar to the default server that appears when you try to create a bluesky account. So… I guess that’s not a barrier after all.
This is the exact reason email never took off. /s
Email was invented in 1983.
It was revolutionary, the utter example of a “killer app” that had people and businesses running out to buy computers just to replace paper memos. You setup your mail server to hook into that brand new, stunning ecosystem of near instant communication from across the world.
Now there are 6,000,000,000 “killer” apps you can install in seconds from your pocket computer. I can hit “install” and be talking face to face with a stranger in Singapore in 30 seconds, all from easy, low effort walled gardens.
Federation was and is a reasonable way to host things, but comparing current systems to email is a misnomer. People dealt with federation because they had to. If gmail has existed in 1983, no one would have had their own federated email servers. Hell, AOL tried to choke the internet itself to death and almost succeeded in the early 90s because it was an “all in one” solution. They had aol only webpages and everything, including email. Its a twist of fate that they failed, mainly due to the onset of always on broadband, not because people didn’t want things easy.
Make things easy, people will use it. They will only do hard if they have to.
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?
Basically, a single instance
If they have the same people running all of them, how is that different from running a single mastodon server in kubernetes, so that it doesn’t get overloaded?
Where?
Let me see how you get instance admins to agree on what to defederate.
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 like the idea of a server choice virtually invisible feature!
Man, it feels like you guys haven’t spoken to a real human in decades…
Yeah, most people wants an easy migration. If the interface was nearly identical to Twitter, there’d be a flood.
The best thing for on-boarding are topic-specific instances, it makes picking one much easier.
Why can’t mastodon influencers create content on how easy it is to pick a server.
Ah make it like a food hall and anthropo the servers as food.