this post was submitted on 07 Sep 2024
11 points (72.0% liked)
FediLore + Fedidrama
2159 readers
23 users here now
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Because a moderator action taken by a mod of a community on a different instance to you, against a user from another instance again, isn't likely to be of any concern to you. It's good that we can access that information, but I would like to be able to filter the modlog to only show local actions, and perhaps the option of a global log.
Otherwise, there's just too much noise.
Of course it is relevant.
That action may be what removed a post or comment from a community you frequent, or a user you like seeing. Or a post you commented on and get left wondering why the post disappeared.
Mod actions don't apply to just the instance the mod or community is on, they apply fediverse-wide on all instances where there are subsribers to that community.
If the admin of MY instance removes one of MY comments, such as this one made in reply to you, you might want to see why.
You can already filter modlogs by user. And if you want to narrow things down more, you ARE aware that each community has their own modlogs that only show actions for that community?
It shows up per default because it affects you. If you like a filter, feel free to file a feature-request on Lemmy's Github.
Make sure to include a proper description of what you'd like and why. Otherwise I doubt it'll get accepted as it makes the modlog a bit counterintuitive to use. Things that affect you everywhere won't show up just because of their place of origin. That might be unwanted on a federated platform. But feel free to disagree, just include your argumentation and let the developers decide.