The real solution would be for the decentralization to be happening in the background and for the platform to be accessible from one website and to let users take care of their own feed themselves.
They only have control in the sense that they can shut down the website, but the content itself isn’t in their control. It would also be possible to have the hosting under a decentralized entity controlled democratically by the people providing the hosting space (à la DAO/DAC in crypto).
I just feel like the whole problem the fediverse is trying to solve is admins slowly selling out and then having to move somewhere else. Having one website still has that problem of switching costs if you want to go somewhere else, you lose access to everything in that sphere of content. If the sh.itjust.works admins go crazy and start moderating in a way you don’t like, you can go sign up on another instance and not lose any of the communities or people you used on your former instance.
But you still rely on the admins of your new instead to decide what content you have access to and on the admins of others instances for the same thing. What I’m saying is that the admins shouldn’t have that kind of power. Heck, the website issue could be solved by having a disconnection between the front and back end.
Decentralize the hosting and make the data available to all (this way all hosts have some of the data but not all of it and you can have all data backed up by other hosts so no host can just nuke part of the website) this way anyone is able to create a frontend. So sh.itjust.works would just show me all of Lemmy’s content in the way the dev decided would be best (the UI would be of their choosing), but I would be the one deciding which communities and users I’m blocking. If I decide I don’t like how my chosen frontend works anymore I could just go and log in to another frontend using the same credentials because the data isn’t hosted on the frontend’s servers.
That is literally the way it works now. As an example - go to https://phtn.app/. Photon is a UI for lemmy. That specific website is hosted by the developer and you can log into any instance. I think Alexandrite and Voyager webapps act the same, but I haven’t tried them, so can’t be sure atm.
No it’s not, your instance of choice isn’t necessarily federated with 100% of all instances. The UI you’re using is loading the content that your instance gives you access to only. Example v I can’t see hexbear communities and they can’t see communities from my instance so the only place I can interact with hexbear users is if they comment on communities both our instances are federated with.
No, each instance can choose what instances it’s federated with so your experience in lazysoci.al can be completely different from mine on sh.itjust.works just like the experience of someone in beehaw or hexbear or Lemmy.world is completely different…
The real solution would be for the decentralization to be happening in the background and for the platform to be accessible from one website and to let users take care of their own feed themselves.
But then it’s centralized on one website and the person who owns that domain has control over the whole
They only have control in the sense that they can shut down the website, but the content itself isn’t in their control. It would also be possible to have the hosting under a decentralized entity controlled democratically by the people providing the hosting space (à la DAO/DAC in crypto).
I just feel like the whole problem the fediverse is trying to solve is admins slowly selling out and then having to move somewhere else. Having one website still has that problem of switching costs if you want to go somewhere else, you lose access to everything in that sphere of content. If the sh.itjust.works admins go crazy and start moderating in a way you don’t like, you can go sign up on another instance and not lose any of the communities or people you used on your former instance.
But you still rely on the admins of your new instead to decide what content you have access to and on the admins of others instances for the same thing. What I’m saying is that the admins shouldn’t have that kind of power. Heck, the website issue could be solved by having a disconnection between the front and back end.
Decentralize the hosting and make the data available to all (this way all hosts have some of the data but not all of it and you can have all data backed up by other hosts so no host can just nuke part of the website) this way anyone is able to create a frontend. So sh.itjust.works would just show me all of Lemmy’s content in the way the dev decided would be best (the UI would be of their choosing), but I would be the one deciding which communities and users I’m blocking. If I decide I don’t like how my chosen frontend works anymore I could just go and log in to another frontend using the same credentials because the data isn’t hosted on the frontend’s servers.
No admins, just community moderators.
That is literally the way it works now. As an example - go to https://phtn.app/. Photon is a UI for lemmy. That specific website is hosted by the developer and you can log into any instance. I think Alexandrite and Voyager webapps act the same, but I haven’t tried them, so can’t be sure atm.
No it’s not, your instance of choice isn’t necessarily federated with 100% of all instances. The UI you’re using is loading the content that your instance gives you access to only. Example v I can’t see hexbear communities and they can’t see communities from my instance so the only place I can interact with hexbear users is if they comment on communities both our instances are federated with.
Isn’t that how it is already.
No, each instance can choose what instances it’s federated with so your experience in lazysoci.al can be completely different from mine on sh.itjust.works just like the experience of someone in beehaw or hexbear or Lemmy.world is completely different…