Hello World,
we know one of the most important indicators of comment and post community interest is votes. Beyond that, reports help to regulate comments and posts that go beyond down-votes and into the rule-breaking territory.
Unfortunately, Lemmy’s current reporting system has some shortcomings. Here are a few key technical points that everyone should be aware of:
- Reports are NOT always visible to remote moderators. (See Full reports federation · Issue #4744 · LemmyNet/lemmy · GitHub)
- Resolving reports on a remote instance does not federate if the content isn’t removed.
- Removal only resolves reports in some cases, e.g. individual content removal. Some people remove individual content before banning the user, especially when the ban is with content removal, as individual content removals resolve reports on all instances. Bans with the remove content checkbox selected will not currently resolve reports automatically.
Our moderators are also volunteers with other demands on their time: work gets busy, people take vacations, and life outside of Lemmy goes on. But that doesn’t mean content that causes distress to users should stick around any longer than reasonable. Harmful content impacts both Lemmy.world users AND users of all other instances as well. We always strive to be good neighbors.
While the devs work on the technical issues, we can work to improve the human side of things. To help keep the reports queue manageable and help reports be resolved in a REASONABLE amount of time we will be enabling global notifications for all stale reports. Open reports older than 1 day will trigger a notification for 1 week every 2 days so as not to overwhelm community moderators endlessly. If a community moderator does not wish to receive these reports, they may simply block the bot, but we still expect them to address unresolved reports.
We expect that this feature will eventually be removed once Lemmy has a better reporting system in place.
As an aside, we recommend that all LW communities have at least two moderators so there is some redundancy in resolving reports themselves, and to reduce the workload on individual moderators. We know this can be harder for smaller communities, but this is just a recommendation.
We recommend that moderators have alt accounts on Lemmy.world to resolve reports that are from federated instances.
As always feedback is welcome. This is an active project which we really hope will benefit the community. Please feel free to reply to this thread with comments, improvements, and concerns.
Thanks!
FHF / LemmyWorld Admin team 💖
Additional mods
We recommend using the Photon front-end for adding mods to your community.
With the standard lemmy-ui, additional mods can only be appointed if the account has made a post or comment in the community.
Photon (https://p.lemmy.world) does not have this limitation. You can use the community sidebar, click Gear (settings) icon, then click the Team tab, and add any user as a mod.
Excellent news! It’s good to hear you’ve designed a workaround to help for outstanding stale reports. Keeping up with moderation is tough.
One thing is unclear to me (and perhaps because I’m still bleary-eyed from sleep), but do these stale open moderator reports go to the assigned Community Mods only? If they persist without action for some time, would they be extended to other mods or admins?
Thats a pretty good idea for this type of bot. I will discuss this with the team. But for admins we have already some analytics for this situation.
Got it. If you have information points upstream for these types of situations that the Admin team already actions, then there’s no point building on top of it to extend stale un-actioned moderator reports to larger teams. Considering the admin team is large here, it may not make sense to spend the cycles to enhance it further.
IIRC, reports are sent at the same time to
yes, but for admins, at least on LW scale, this isn’t something that is well usable for admins with built-in tools.
community mods and instance admins can see reports on the instance that reports are sent to, and they are currently only sent to the reporters instance, the community instance, and the reported users instance. community mods on another instance won’t see the reports.
Yeah it’s been manageable on our instance so far. I’d say our admin team manage most of the reports if the community mods don’t get to them within an hour or two. Works well for smaller instances, but I can see how it wouldn’t scale well at LWs size.