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?
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.
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.)
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.
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?
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…
The best thing for on-boarding are topic-specific instances, it makes picking one much easier.
Yeah, most people wants an easy migration. If the interface was nearly identical to Twitter, there’d be a flood.
So what, should we have a website where you push a button and it sends you to a random instance to sign up?
Just imagine the surprise when a new user is placed in hexbear or one of the porn servers.
Then it was fate and they should just accept it.
oof, i learned about hexb the hard way, so i feel for these hypothetical users already.
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 would be the incentive for people to do that?
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.
I liked the community that had built up and wanted to help that continue.
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.
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.
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.)