this post was submitted on 25 Jan 2025
64 points (98.5% liked)

196

1839 readers
2520 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
 

cross-posted from: https://sh.itjust.works/post/31615576

There have been messages going around the federal government with these emails listed to "report" anything

DEIATruth@omp.gov (main email sent to employees)

DEIAreports@omp.gov (address given to agency heads)

amanda.scales@opm.gov (address given to agency heads)

The government memorandum with these emails spelled out


I've seen people mentioning that they will probably filter for .gov email addresses. Here's how we can flood all those emails with .gov emails

.gov Newsletters

Federal agencies, states, US territories, counties, cities & other localities have .gov domains and many of them have automated email newsletters. Sign these addresses up for as many of them as you can. Some of those news letters will probably not be sent from the actual .gov domain, but others probably will. Our goal is sheer numbers here

When you sign up, put as many keywords as you can in the first name field. Newsletters often say your first name, so we can make keyword search a pain for them. Can even add some LLM prompt injections to limit their searching through that

You can find some of those newsletters with searches on any search engine like this:

[insert agency/state/locality] email newsletter site:.gov

So for instance search

Nebraska email newsletter site:.gov

Spoofing emails

These are much more likely to not get through and be blocked by filters but it's worth a try to see if it will get through. Not going to go into too much depth here, so only do this if you know how to

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here