this post was submitted on 20 May 2026
399 points (99.3% liked)

196

6257 readers
1977 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
 

Alt TextBluesky post by user @magnusbeefcastle.bsky.social that reads,

I INSTALLED “LINUX”. BECAUSE WINDOWS IS FOR MEN WHO ASK PERMISSION TO EXIST. I CRUSHED THE INSTALLER WITH MY BARE HANDS AND NOW THE TERMINAL CALLS ME “SIR” BUT MY KERNEL KEEPS PANICKING. WHAT COMMAND MAKES THE COMPUTER SUBMIT COMPLETELY? I REFUSE TO GOOGLE

Link to original post

~Yes, all of this user’s posts are like this.~

you are viewing a single comment's thread
view the rest of the comments
[–] lime@feddit.nu 42 points 22 hours ago (1 children)
:() {      # define a function named ":".
 :         # run the function named ":"
   | :     # pass the output to the function named ":"
       &   # run this line in the background.
};         # end of definition
    :      # call the function ":".

in case anyone was curious.

[–] rbos@lemmy.ca 12 points 22 hours ago (2 children)

If you replace : with "loop" it becomes pretty clear. The only 'weird' thing is using punctuation as a function name.

[–] Wirlocke@lemmy.blahaj.zone 3 points 6 hours ago (1 children)

I think it's meant to be confusing. If you're unfamiliar with code, you'll likely glaze over the random string of symbols and assume it's like broken HTML or JSON or something.

Hell even if you are a programmer, I think most programmers assume you can't use a colon in a variable or function name, much less just a colon.

[–] rbos@lemmy.ca 4 points 6 hours ago* (last edited 6 hours ago)

Definitely. But it's worth expending some skull meat to understand what's going on. :)

In some of my university classes I liked to use Hiragana characters (from Japanese) for variables and function names, just to be a jerk.

[–] lime@feddit.nu 13 points 21 hours ago* (last edited 21 hours ago) (1 children)

it's not just looping; every instance starts two instances of itself waiting for input. it's basically doing

async def fork(): 
    f = fork()
    await fork(await f)

...except python doesn't start the second call until its arguments are evaluated, while shell does.

[–] rbos@lemmy.ca 4 points 7 hours ago

Yeah, "loop" was a poor choice of keywords. My point was that replacing : with a more plain identifier helps it make sense. :)