Seems like everything is up to date on lemmy.dbzer0 now, just minor federation quirks it seems like. Thanks for notifying about a potential issue.

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.

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:

From the PR standpoint, I don’t think it’s worth it, and it’d be better to just leave it on reports.

The problem is that we can’t rely on reports of DMs since lemmy doesn’t federate them to us.

E.g.
-> troll@programming.dev makes a new account and sends harassment to victim@lemmy.instance
-> victim@lemmy.instance reports the DMs from troll@programming.dev
-> We, the admins of programming.dev, do not see this report because lemmy does not federate the DM report and troll@programming.dev can continue harassing others because we never find out about it.

This isn’t just a theoretical, it happened just last month that one of our users (1 day old account) sent rape and death threats (which were reported), and we found out about it by pure chance when talking to admins from the other instance.

And just to clarify, the tool only automatically monitors new accounts, i.e. accounts that are being registered today. If you account is more than a few weeks old, the tool doesn’t monitor any of your activity.

It’s not about the profanity itself, it’s about what language the trolls/harassers typically use. The comment containing profanity was restored after it was seen to not be harassment. Most new users doesn’t trigger the automod in the supervision period.

The instance has experienced a lot of trolls signing up recently, so we need to moderate new accounts more strictly. The automated removal is needed to respond quickly to potential harassment. The comment was restored after manual review.

Please follow our instance’s Code of Conduct and avoid using slurs, repeated breaches will lead to a temporary ban from our instance.

Hi

Can you update the title to be the same as the updated title in the news article?

The (successful) end of the kernel Rust experiment

Hi, I’ve sent you a new DM

Hey

Please check your DMs, you got unresolved reports from c/linux

It’s not helping if some bitch on her menstrual cycle comes and spams her keyboard without any valid points

You’ve already previously been given warning for breaching our Code of Conduct section 3.5 (Hate Speech: Do not make remarks directed at sex, gender…). This is your third strike within 2 months and your account is now at risk of receiving a permanent ban if further breaches are made within 365 days.

Since this is strike 3, your account will be given a 14 days site-wide temporary ban.

- The programming.dev community team

If you don’t have anything positive or helpful to say, it would be better to just not reply. If you think the post shouldn’t be posted here, use the report function instead.

Please don’t stalk/harass our users, it can and will lead to a site wide ban if reported.

Reminder that our Code of Conduct (3.2, 3. 5) applies even on communities outside our instance. If you keep breaking those rules we may give you a temporary ban.

This is your second warning to not break our CoC (3.2).

A third warning will result in a temporary ban from programming.dev.

Remember that our CoC applies even on communities outside our instance. Try to avoid personal attacks and telling people to harm themselves per CoC 3.2 and 3.7. Continued failure to do so will lead to a temporary or permanent ban.

Just a reminder that our instance CoC applies even on communities outside our instance. Please try to avoid calling people slurs per CoC 3.2 and 3.5. Failure to do so may lead to a temporary or permanent ban.

Looking at your instance handle, I hope/assume that your comment is supposed to be in lighthearted jest. However that would only be an assumption on my part and in general it’s not ok to say someone’s job/work tool is for [remarks directed at sex, gender, ethnicity, orientation, disabilities, etc…] per CoC 3.5.

Please take into consideration that members on this instance may be of different backgrounds than what you’re used to and interpets what you say differently. Further breaches of our Code of Conduct may lead to temporary or permament ban.

deleted by creator