-34
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jun 2025
-34 points (11.4% liked)
FediLore + Fedidrama
2977 readers
4 users here now
Rules
- Any drama must be posted as an observer, you cannot post drama that you are involved with.
- When posting screenshots of drama, you must obscure the identity of all the participants.
- The poster must have a credible post and comment history before submitting a piece of history. This is to avoid sock-puppetry and witch hunts.
The usual instance-wide rules also apply.
Chronicle the life and tale of the fediverse (+ matrix)
Largely a sublemmy about capturing drama, from fediverse spanning drama to just lemmy drama.
Includes lore like how a instance got it's name, how an instance got defederated, how an admin got doxxed, fedihistory etc
(New) This sub's intentions is to an archive/newspaper, as in preferably don't get into fights with each other or the ppl featured in the drama
Tags: fediverse news, lemmy news, lemmyverse
Partners:
founded 2 years ago
MODERATORS
I guess it could functionally be an instance ban if literally every single comm moderator got together and banned a user from every single comm on an instance...
But I am not seeing that. I am seeing a slew of users getting banned from 2 or 3 comms focused on different kinds of AI-gen art, because they've been virulently anti-ai art in those comms and elsewhere.
Its also fairly common for a single person to be a mod of several smaller niche comms... and if the whole thing is that they've identified a person as combatative troll who breaks other various rules in other various places... then yeah, they just get put on a shit-disturber/troll blacklist, for those comms that are small and basically function as safe spaces for small groups.
As I understand it, as I read the modlog... these users you've included in your post screenshots and such are not literally banned from the entire dbzero instance, nor all its comms... if either of those were the case, you could see it in the modlogs.
Again, as I understand it... while modlogs obsure the name of the moderator or admin taking an action... all actions are otherwise detailed in full.
It's more like a federation glitch. The modlogs don't always represent a situation correctly. Hence what you said after that. On my end, it appears as multiple communities. So I stand corrected.
General best practice for viewing modlogs:
Go to the actual instance's website and view their own modlog.
That's why I provided the link to it my post a couple levels up. Sometimes silly stuff can happen if you don't do it that way.
Also, for what its worth, I'm not the one throwing the single downvote on these more recent comments between us.