this post was submitted on 06 Jun 2023
13 points (100.0% liked)
Lemmy Support
4650 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Its not a bug but the mod log could use better filtering.
I don't think the perceived bug is that the bans show up in the mod log. The perceived bug is that bans propagate, i.e. a user banned in lemmy.ml is also apparently banned in every other instance that federates with lemmy.ml
Nah, I believe it's just that a user that registered with lemmy.ml originally and is then banned in lemmy.ml can't interact with anyone. The instance basically stops supporting that user. That's kinda important, because an instance is in some ways responsible for their users.
If an instance gets a whole lot of brigading from users from a given instance, then they might consider blocking that instance. An instance blocking its own user is taking away their ability to represent that instance on any level.
They can obviously still go registered with another instance.
Yes, everything you said is correct and good. But it has nothing to do with why a user on lemmy.ml, who was banned by lemmy.ml shows up in the ban list for my instance.
Right, I agree that that's weird UX. It's probably down to the way the federation works. I just wanted to clarify so that people didn't think that one instance has the power to ban users from accessing other instances.
I'll check the Lemmy issue tracker and submit an issue if one doesn't exist. There's some adjustment that has to happen there.
Nice username by the way