this post was submitted on 14 Aug 2025
681 points (91.8% liked)

196

4159 readers
1988 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 6 months ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] uuldika@lemmy.ml 1 points 2 days ago

i think it depends on what you're doing, maybe. like I set up sops-nix to manage my secrets, but I wanted to use a Yubikey to protect the master key, so I had to use age-plugin-yubikey... only to discover that sops-nix ignores environment.SOPS_AGE_KEY_CMD for some reason, so I had to point at a random PR on sops-nix to enable experimental plugin support, or dig in and override the sops pkg. then I ran into issues where (I think?) wireguard was coming up before the sops secrets trigger, and failing because it couldn't read the private key.. and then on my WSL2 environment I have to do even more since I cross-compile age-plugin-yubikey to Windows x64 from inside my NixOS build, but then I had to pin a bunch of cargo packages because the repo didn't ship with anything pinned... and for SWI-Prolog I had to roll my own system for adding modules to it, since the nixpkgs support for that is hilariously broken and fully recompiles SWI-Prolog from scratch every time... and now I'm thinking of setting up a microvm with Wayland forwarding for tor-browser but I can't imagine how much harder that will be...

...but also like, I can't imagine doing all of this by hand ever again. once I get my janky-ass nix config working, it'll keep working for as long as fetch urls stay green (which is a big issue unfortunately.)