It's the lemmy modlog, it shows all federated actions.
You can see the same thing for lemmy.world here:
this post was submitted on 07 Sep 2024
-2 points (0.0% liked)
FediLore + Fedidrama
2754 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 did have a look at their modlog for comparison. It seems counterintuitive that an action taken by a mod on another instance would show up in theirs. Wouldn't the act of banning someone inherently federate by the fact their posts would no longer be seen?
I think part of it is transparency. As a mod on lemmy.world, it benefits me to be able to look at the modlog and see a users entire history, not just on lemmy.world.
That's federation. You're on lem.ee, still you don't want all the spam and deleted content to show up when you visit the news community on lemmy.world. That community has some mods and they keep the community clean. And not just for their instance. It needs to spread throughout the network. So naturally every mod action shows up on lem.ee dubvee and everywhere after the originating instance forwards the action to them. Or you'd have a vastly different view on the same community, depending on viewpoint.
I get that, but can't those actions federate without showing up in the modlog for everyone? Or have the option to only see actions from that instance in the log?
All mod actions on all instances and communities are relevant, why would users on a given instance only need to be able to see modlogs for their own instance?
They are interacting with the whole fediverse, so why shouldn't they have access to the log of mod actions on the whole fediverse, too?
If I'm on my instance, and get banned from a community by a mod on another instance, in a community on another instance, I would still want to be able to check when and why that happened in the modlog on MY instance.
Or if some other user I know has disappeared, wherever mod actions have been taken agaibst them, should still show up on my instance.
I don't know what client you are using, but the default webUI can apply filters and do searches in the modlog.
Mostly, I feel it adds clutter to the log, and is only tangentially related to the instance.
It's good that we can see it, but I feel it would be better if we could filter it out.
How is displaying mod actions from federated communities any more "tangential" than displaying the posts from them in the "all" feed?
It's like asking why anyone would ever need more than the "local" feed.
You can filter the modlog to only show actions related to a given user, which is by far the most useful one, and you'd want that to include ALL relevant entries, on or off-instance.