cross-posted from: https://programming.dev/post/51288619
Hi All,
Due to some ongoing issues with harassment campaigns, we’ve had to setup a rudimentary monitoring system for all new users.
- When a user’s signup is accepted, they will be automatically enrolled into the monitoring system. The admins team may also add accounts manually if they have been given a strike.
- The system will monitor all posts, comments and DMs sent by new users, and bring them to the attention of the admin team if it appears suspicious. In egregious cases, it will auto-remove posts and comments if required, but a human admin will always review and reverse any false positives as soon as required.
- Once we have validated that the user is not a spammer, they will be removed from the system.
We don’t want to go into too much detail on how it all works, but we can say that all the processing is being done locally on the instance server. For most of you, this wont have any impact, but some of you have been impacted by the systems false positives. It is also a good time to point out that DM messages are not private, and should not be used for anything that requires strong privacy.
There will likely be teething problems, but we are actively working on improving the bot to minimize impact and we are always open to feedback.


I welcome all ideas to curb abuse but reading DMs seems a bit much. I figure users can report abusive DMs, which could then be viewed instead of looking at them before hand?
That being said, I find it hard to think of new users sending legitimate DMs. I have done it once I think during my entire time on Lemmy.
I’ll copy the answer I provided in the main thread over on !meta@programming.dev, but to also add, the tool does not monitor all users. It only monitors newly created user accounts on programming.dev for x amount of time so that we know that the account isn’t being made to abuse or spam. We do not want to have this tool monitoring regular users.
Copied reply about why DM monitoring is needed:
Ohhh, I see the problem with the non-federating reports. That does make these measures much more understandable, although it sounds like it’s not receiving the reports that needs fixing overall.
It’s an open issue on github from 2024, it doesn’t seem to be a priority. This tool allows us to react faster than reports though, and hopefully remove some problematic content before it’s seen by others.