this post was submitted on 12 Mar 2026
73 points (98.7% liked)

196

5877 readers
2694 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 1 year ago
MODERATORS
 
top 19 comments
sorted by: hot top controversial new old
[–] theunknownmuncher@lemmy.world 21 points 1 day ago (2 children)
[–] lmr0x61@lemmy.ml 33 points 1 day ago (3 children)

If somehow you haven’t read the canon of YAML haters (among which I count myself), you gotta check out The YAML Document from Hell. It’ll make you seethe with holy rage.

tysm for sharing that article, is good!

This is every yaml document

[–] rtxn@lemmy.world 11 points 1 day ago (1 children)

Almost all of those issues are solved by quoting the string values.

[–] theunknownmuncher@lemmy.world 12 points 1 day ago (1 children)

Oddly it does not even mention the biggest sin and problem with YAML: semantic whitespace.

[–] Swedneck@discuss.tchncs.de 5 points 1 day ago

i get semantic whitespace in python, it makes it less scary for beginners and i personally find it objectively easier to read.

But for config files (which afaik is the whole point of yaml) the parens don't even get in the way, they're actively helpful to find where a section of the config starts and ends! aurgh

[–] Sv443@sh.itjust.works 11 points 1 day ago (1 children)

Thanks for the name idea. Version 1 of the GIHY spec will be out tomorrow.

[–] theunknownmuncher@lemmy.world 9 points 1 day ago (1 children)

The spec should just be identical to JSON

But with comments this time

[–] zea_64@lemmy.blahaj.zone 10 points 1 day ago

Say Norway to YAML

who asked for this

[–] lmr0x61@lemmy.ml 14 points 1 day ago

All my homies hate YAML

[–] als@lemmy.blahaj.zone 1 points 21 hours ago

we really didn't need the 15th standard

[everyone hated that]

[–] QuinnyCoded@sh.itjust.works 11 points 1 day ago (1 children)
[–] xkbx@startrek.website 12 points 1 day ago (1 children)

Imagine everyone using Latin to program

Someone comes along and says we’re using Jenglish now

[–] irelephant@lemmy.dbzer0.com 2 points 19 hours ago

Its more like someone picking toki pona for a protocol, which everyone hates and tries to work around without vulnerabilities and other jank, and then the w3c introducing a worse toki pona based on english