this post was submitted on 04 Jun 2025
19 points (75.7% liked)
[Closed] Moved to !fedigrow@lemmy.zip
1584 readers
1 users here now
This community has moved to !fedigrow@lemmy.zip
Original sidebar info
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- !fedibridge@lemmy.dbzer0.com to organize overall fediverse growth
- !reddit@lemmy.world to keep tabs on where new users might come from :)
- !newcommunities@lemmy.world
- !communitypromo@lemmy.ca
Megathreads:
- How (and when) to consolidate communities? (A guide)
- Where to request inactive or unmoderated communities? (A list)
Rules:
- Be respectful
- No bigotry
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd say under 24h is kinda harsh given I can see small instances get autolocked when the one mod is just on holiday or something for a report about idk, a post being offtopic (for instance)
Yeah, and if someone knows the mod is AFK, they could game it with false reports to lock the community.
The login tokens are long-lived, so that'd be hard to track unless they login from different devices. I don't think the API provides any way to tell the "last activity" of a user aside from the last time they posted/commented.
It's a good idea, but I just don't think Lemmy has the requisite "tracking" to make it work right now.
In theory since reports are attributable false reports would get someone banned (from the community at least) for report abuse. It's not a perfect proposal, but the bones are here to enforce distributed workflows off the admin's shoulders.
Yet in the meantime, it can cause communities to lock-up. I would argue a week is more realistic. Plenty of communities are that abandoned.