That’s because you’ve chosen an instance that is more heavily curated. You can check which instances yours has defederated from at sh.itjust.works/instances
But if you look at the same page on mander.xyz/instances my admins are only defederates from threads.net and burggit.moe, so I already experience the fediverse as you describe.
But other instances can choose to defederste from Mander so their users can’t post on Mander’s communities, it’s a two way street. Just the fact that it’s defederated from those two should make you understand that you as a user don’t control the content you have access to, an admin decided that threads and burggit would be inaccessible to you.
The solution I’m talking about eliminates that completely, treat the hosting the same way any other website works (a bunch of servers hosting the data with redundancy, the difference being that it’s people like you and me providing the storage space instead of an all in one service like AWS), make access to that data open and let people create a UI for users. No more defederation or admins that hold power over all communities under the umbrella of an instance, just community mods and a website where users are the ones in control of their experience.
While I agree that an IPFS solution could be quite resilient, I’m not sure that the average person is willing to put up the resources or risk of hosting content. CSAM, copyright, etc, all become more of an individual risk that you’re relying on moderators to mitigate for you. (Rather than the risk going to the server hosts typically doing the moderation covering their own ass)
Additionally, while there may be decent representation of people willing to do some small amount of hosting of services (myself included) on lemmy, I think making this mandatory really limits the growth of your social media platform.
I think you could achieve what you’re looking for right now by self-hosting a private lemmy instance with signups closed, and this wouldn’t close you out of existing federating platforms.
The people currently doing the hosting would be the same ones doing the hosting (I’m not talking about every user hosting their own content), they just would choose to host NSFW content or not as they already do by choosing to allow NSFW communities on their instance or not (and would use the necessary tools to cleanup their storage of illegal content as they already do) and users who choose to activate NSFW content in their feed would do it at their own risk (which is pretty much already the case anyway because instances/communities with CSAM don’t get deleted/banned/defederated until someone does it, it’s just your/the other instance’s admin that’s doing it instead of you).
That’s because you’ve chosen an instance that is more heavily curated. You can check which instances yours has defederated from at sh.itjust.works/instances
But if you look at the same page on mander.xyz/instances my admins are only defederates from threads.net and burggit.moe, so I already experience the fediverse as you describe.
But other instances can choose to defederste from Mander so their users can’t post on Mander’s communities, it’s a two way street. Just the fact that it’s defederated from those two should make you understand that you as a user don’t control the content you have access to, an admin decided that threads and burggit would be inaccessible to you.
The solution I’m talking about eliminates that completely, treat the hosting the same way any other website works (a bunch of servers hosting the data with redundancy, the difference being that it’s people like you and me providing the storage space instead of an all in one service like AWS), make access to that data open and let people create a UI for users. No more defederation or admins that hold power over all communities under the umbrella of an instance, just community mods and a website where users are the ones in control of their experience.
How do you deal with CSAM and hate speech instances? Those are generally the ones everyone wants to defederate from
Hosts and users get the choice to turn NSFW content on or off at their own risk (for hosting and for seeing in their feed respectively).
Hate speech isn’t illegal to see, users would block communities/users by themselves.
While I agree that an IPFS solution could be quite resilient, I’m not sure that the average person is willing to put up the resources or risk of hosting content. CSAM, copyright, etc, all become more of an individual risk that you’re relying on moderators to mitigate for you. (Rather than the risk going to the server hosts typically doing the moderation covering their own ass)
Additionally, while there may be decent representation of people willing to do some small amount of hosting of services (myself included) on lemmy, I think making this mandatory really limits the growth of your social media platform.
I think you could achieve what you’re looking for right now by self-hosting a private lemmy instance with signups closed, and this wouldn’t close you out of existing federating platforms.
The people currently doing the hosting would be the same ones doing the hosting (I’m not talking about every user hosting their own content), they just would choose to host NSFW content or not as they already do by choosing to allow NSFW communities on their instance or not (and would use the necessary tools to cleanup their storage of illegal content as they already do) and users who choose to activate NSFW content in their feed would do it at their own risk (which is pretty much already the case anyway because instances/communities with CSAM don’t get deleted/banned/defederated until someone does it, it’s just your/the other instance’s admin that’s doing it instead of you).