Not really. You can just switch instances if you’re not happy with your admin’s policies. Although figuring out who is federating with whom could be a bit more straightforward.
The alternative would be giving no option of defederation and making live a living hell for mods and admins. They’re already doing unpaid work in almost all cases so nobody would profit from driving them towards burnout, which is still all too common as it is.
I see a future where the Lemmy clients can get feeds from multiple instances, and blend them for you. Let’s just consider if you’re a new user on a new instance, there’s nothing in the local feed so it feels empty, I expect clients to allow you to look at the feed from other bigger instances, to help populate your subscription list, and your comments would still come from your home instance.
In this environment, one instance censoring you wouldn’t have a big effect, cuz you would still be in the feed
Umm, all of what you are describing already exists and is basically how lemmy works. The local feed would always be empty on your newly setup instance if course, precisely because it is the “local” feed.
If you want to see the feed of all the instances you are federating with, that’s “all” (or whatever it’s called on your specific client).
The all feed only populates data that your local instance is aware of. So if you have a new instance that isn’t aware of any communities, you’re all feed is empty.
It really is though. You have to know about which communities to subscribe to to get them federated on your instance. Which is a pain in the butt. It’s not a good workflow. You’d have to use some external Lemmy community website, convert the link into the bang link, then put it into your mobile client. And then subscribe. It’s a terrible workflow.
It’s extremely high friction, which means smaller instances are only going to know about the large communities that people bother to do it for.
Am I hopeful this workflow gets better? Absolutely! I have faith that this workflow will get better on many clients. But right now it’s high friction very high friction
Oh, okay, so you’re talking about a case scenario where you’re on a small/new instance that also isn’t your own. Got it, dunno why I was making a different assumption. Yeah, I can see what you’re talking about then.
People not wanting to engage with other people is not censorship. Nobody is entitled to someone else’s attention.
deleted by creator
I agree but here we are talking about preventing potential people who would like to hear, read or see certain posts
Not really. You can just switch instances if you’re not happy with your admin’s policies. Although figuring out who is federating with whom could be a bit more straightforward.
The alternative would be giving no option of defederation and making live a living hell for mods and admins. They’re already doing unpaid work in almost all cases so nobody would profit from driving them towards burnout, which is still all too common as it is.
I see a future where the Lemmy clients can get feeds from multiple instances, and blend them for you. Let’s just consider if you’re a new user on a new instance, there’s nothing in the local feed so it feels empty, I expect clients to allow you to look at the feed from other bigger instances, to help populate your subscription list, and your comments would still come from your home instance.
In this environment, one instance censoring you wouldn’t have a big effect, cuz you would still be in the feed
Umm, all of what you are describing already exists and is basically how lemmy works. The local feed would always be empty on your newly setup instance if course, precisely because it is the “local” feed. If you want to see the feed of all the instances you are federating with, that’s “all” (or whatever it’s called on your specific client).
The all feed only populates data that your local instance is aware of. So if you have a new instance that isn’t aware of any communities, you’re all feed is empty.
Ok fair enough, but that isn’t exactly a hard hurdle to overcome.
It really is though. You have to know about which communities to subscribe to to get them federated on your instance. Which is a pain in the butt. It’s not a good workflow. You’d have to use some external Lemmy community website, convert the link into the bang link, then put it into your mobile client. And then subscribe. It’s a terrible workflow.
It’s extremely high friction, which means smaller instances are only going to know about the large communities that people bother to do it for.
Am I hopeful this workflow gets better? Absolutely! I have faith that this workflow will get better on many clients. But right now it’s high friction very high friction
Oh, okay, so you’re talking about a case scenario where you’re on a small/new instance that also isn’t your own. Got it, dunno why I was making a different assumption. Yeah, I can see what you’re talking about then.