this post was submitted on 10 Sep 2026
25 points (93.1% liked)
Fediverse
43850 readers
558 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Only if that scale happens across the current number of servers. If the server base grows along with users the manual management may scale much better
Unfortunately Lemmy has one major problem when it comes to banning spam bots. Only the instance that a user belongs to can ban the user in a way that federates to other instances. This means if that particular instance doesn't quickly ban the user, then hundreds of other instances need to do it manually. Currently, a pretty significant percentage of spammers get banned individually by many instances.
If we had 100x as many users and 100x as many instances, we would have 100x as many bot accounts for every instance to ban.
The solution is probably something like shared ban lists or ban mirroring (setting an instance up to ban every user that some trusted instance bans). But right now it's just people clicking, and it's not scalable.
This could be mitigated quite easily by having a clear separation between instances run for users and instances for communities.
Can you explain some more? I don't get how this separation helps unless you keep a small number of community instances.
Yes, I think you get it. My assumption is that there would be a lot less of "community instances" compared to "user instances".
Hmm, yeah that seems like it does need a technical solution
Thank you for taking the time to explain! ☺️