I’m not sure I agree with this one, actually. If one of our users is banned from a remote instance for reasons I disagree with, I might still want them to be able to talk to our users in the comments on that remote community.
The trouble is that if they're a problem user, and being realistic, many would be - the community moderators wouldn't be able to see what's going on as the comments they post would not federate out. They would effectively be unmoderated.
We had a situation where a user recently banned from lemmy.blahaj.zone was still posting gore to lemmy.blahaj communities on their instance. Obviously it wouldn't federate out, but people on that same users instance would still see it.
That's what prompted me to try and deal with this issue, at least from Piefed's perspective.
The last part is not included with the new changes. Basically this change only effects piefed-based users. I was suggesting at the end that a way be incorporated from Piefed's end to automatically throw out comments or posts from Lemmy users posting in instances they're banned on so that they don't even appear locally on their instance - but that isn't currently possible.
We have to wait for Lemmy to implement this change from their end for it to be universal.
I think people consider sexual assault differently here, although I'd note that Harry Potter is probably way more of a global phenomenon than Gaiman's stuff which plays into this too.
On Reddit, if I write a post in a subreddit and click Post, it is stored on Reddit’s servers, and anyone with a Reddit account can access Reddit’s servers and see it because we’re accessing the same monolithic system. On Lemmy, I’m currently posting to lemmy.world from a sh.itjust.works account in response to an account from programming.dev. On which of those three independent platforms will this message be stored? How could someone from, say, piefed.social see it? I genuinely don’t understand this fully msyself and I’ve been on Lemmy for a couple years now.
It's stored on all of them. Piefed.social can see them because piefed.social is federated with sh.itjust.works, lemmy.world and programming.dev.
There's one major oversight here that needs to be addressed if Lemmy/Piefed were to suddenly gain a glut of new users. How bans work.
Currently, instance bans and community bans are treated as two separate things. When a user is banned from an instance, you'll often see in the logs a bunch of community bans alongside it at once. These are communities that user has posted on. An instance ban automatically applies hard-bans to communities they have interacted in from that instance. But the problem here is its only communities they've interacted in.
The instance ban itself is simply a rejection of federation. It doesn't block users from posting in communities on that instance - only the community bans do that. It just means their posts won't federate out. This means that an instance banned user can continue to be a nuisance in most communities (or all, if they are pre-emptively banned) on an instance locally - and the moderators of that community and instance won't even know. With larger numbers of users would also mean larger amounts of trolls and incompatible users, which could greatly increase the chance of people simply vandalising communities and no-one even noticing.
Tbf piefed.zip doesn't have much of a local so that makes sense for you, but the user above is on feddit.org, which is a long-running German-language (at least prominent) instance so it does make sense for them in that context if they're German.
The trouble is that if they're a problem user, and being realistic, many would be - the community moderators wouldn't be able to see what's going on as the comments they post would not federate out. They would effectively be unmoderated.
We had a situation where a user recently banned from lemmy.blahaj.zone was still posting gore to lemmy.blahaj communities on their instance. Obviously it wouldn't federate out, but people on that same users instance would still see it.
That's what prompted me to try and deal with this issue, at least from Piefed's perspective.