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 I’m 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.
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.
The authentication could be another service, split from Mastodon, Lemmy, Pixelfed, … that only gave that service. The instance asks the auth server about “user@instance: password” and the server just says “OK/fail”. That or sending the user to the auth server to get a session cookie.
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.
So what, should we have a website where you push a button and it sends you to a random instance to sign up?
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 I’m 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.
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.
The authentication could be another service, split from Mastodon, Lemmy, Pixelfed, … that only gave that service. The instance asks the auth server about “user@instance: password” and the server just says “OK/fail”. That or sending the user to the auth server to get a session cookie.
Just imagine the surprise when a new user is placed in hexbear or one of the porn servers.
oof, i learned about hexb the hard way, so i feel for these hypothetical users already.
Then it was fate and they should just accept it.
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.
Yes honestly, we can manage what instances are pooled for on boarding.