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.
You must log in or register to comment.
Nice feature.
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.
Sounds like a reasonable recommendation.
The upcoming v20.0 lemmy release should fix remote moderators not receiving almost all of the reports.
https://github.com/LemmyNet/lemmy/issues/4744
Then I’ll be able to moderate !asklemmy@lemmy.world actively from my programmings.dev account and finally abandon this account for the time being.
I wouldn’t completely disregard remote moderators breaking again at some point again in the future, but you do you 😄
That would also require world to update lol
Are you implying that world won’t update? You’d be wrong.
They are teasing about LW’s longer updates timeframes.
They are the last instance in the top 20 (by monthly active users) still using 0.19.3 with Beehaw: https://fedidb.org/software/lemmy
I’m pretty sure the LW admins explained why they didn’t upgrade to 0.19.5 and that they were waiting for 0.19.6.
Honestly wondering if they’ll update at all while waiting for sublinks which is totally ready any day now
we aren’t holding back on lemmy updates due to sublinks.
Thanks for clarifying, I don’t know why goferking thought that
Maybe I was thinking of beehaw. Some admin was saying it was going to be out any day now before summer started
Thanks for this. I never noticed I had a 3 week old report open on a LW community I modded because it never federated with my instance.
What’s a “remote moderator”?
My Dad when he needs to watch football
a moderator on another instance than the community instance
Thanks
On the multiple mods thing. It’s also worth having multiple mods in multiple time zones so there is overlap.
Is the bot broken or was this just a test?
There were two brand new reports and I got this:
that was a logic flaw for the selection of which reports are considered for alerting. a fix is currently being deployed, but you should be good for the next 2 days anyway.
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
- community mods
- community admins
- reportee admin
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.
Good idea to double up on mods. I added a new mod to Artshare, and looking for another for Cooking.
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.
I’d like to add that, while it’s not bad to add someone with moderating experience, you should see how many communities that person already moderates. I get asked to moderate new communities sometimes and I always have to turn them down because my voluntary workload is heavy enough as it is.
Whelp, I considered 8h to be long for addressing issues, but I have no life… Classic mod style 😎
All I ask is, if you see something, flag it. That doesn’t mean I will always take action, but it is always appreciated just the same.
A good mod is an invisible mod to almost all users. In fact, I really wish we could institute this distinction as a part of Lemmy code and culture, (but it might be untenable with people of different personalities). I wish I did not have a mod tag by default. If I choose to act as a mod, I have the option to add the tag.
In a perfect world, if a mod interacts with users directly in a conversation, they would be blocked from escalating privileges to the mod tag and taking actions against the user. They would be required to keep an extra active mod for the community, with a unique history and IP address that would be able to address any flags they or others create. Such a system would solve a lot of bad-mod complaints that are universal to link aggregation platforms. This requirement would force objective judicial thinking that is more resistant to biases and emotions. It would also press active communities to expand their pool of franchised users by adding extra mods, likely increasing post quality and frequency by those that feel a little more motivated to lead in active posting. The last aspect I can think of off the cuff is that it would likely require an extra layer of Admin notifications and awareness in very rare instances where multiple mods have engaged within a single conversation and then it has become an actionable issue, then it would require admin actions. Really, applying such a system to everyone except the root admin owner would be a way to use checks and balances to ensure healthy balanced oversight in all instances. It is essentially rejecting the persistent root super user login and instituting a sudo type escalation layer for mods and admin but on a more social level.
Good feature! Notified me that we had a report that I otherwise wouldn’t have noticed!
Can we have some way for reports to bypass mods with their own op?
Example, stop loli. I reported this but I have a feeling op just closed it.
deleted by creator
Test recieved lol
