this post was submitted on 04 Feb 2025
463 points (98.7% liked)

196

1906 readers
2513 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 2 weeks ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 2 days ago* (last edited 2 days ago) (2 children)

Is there something that can be done across Lemmy to prevent mass spammers? Surprised nobody used this before. Got messaged twice so far.

[–] [email protected] 7 points 2 days ago (1 children)

One defense could be for an instance admin to set a maximum number of messages someone can send to different accounts on their instance per hour.

This would be a heuristic approach to combat spam but this function would first have to be implemented by the Lemmy developers.

[–] [email protected] 2 points 1 day ago

honestly it always astounds me that developers don't pre-emptively add ratelimiting, it's such a basic thing to prevent misuse

[–] [email protected] 4 points 2 days ago* (last edited 2 days ago) (1 children)

i guess it's a case of each instance admin whacking these moles as they pop up. also having anti bot signup defenses.

I'm guessing there's also stuff that could be done server side to stop single accounts sending the same message to > 100 people or something like that. not sure if that's already implemented though.

[–] [email protected] 1 points 2 days ago (1 children)

That seems like a lot of work that admins would have trouble keeping up with.

Theoretically couldn't they keep setting up their own new instance on a daily basis?

[–] [email protected] 3 points 2 days ago* (last edited 2 days ago)

There is a cost associated with setting up each new instance, domains cost money. Time and effort would have to be invested in automating the set up and teardown of such instances on a daily basis (if the scammer has the ability to do that otherwise they'd be doing it manually). Spammers don't tend to like to spend any money

federation, from what i understand, requires active users to fully integrate with other instances so lots of PMs coming from federated instances with little to no active users would be detectable i would imagine.

There are technical solutions to these problems. as with any platform, it is always an arms race between spammers and the developers/moderation teams.

Mod tools are useful in automating this sort of stuff but some things are better handled at the low level by Lemmy developers.

I looked into creating some mod tools to help with this sort of thing a year or so ago, but i'm a backend guy if i'm anything dev wise. CSS did what CSS does and gave me a big enough headache to quit