196
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.
view the rest of the comments
Old joke , its a fork bomb !
Can you explain for us casuals?
So, it uses the fact that bash allows functions with non-alphanumeric names, in this case it defines a function called
:. If we rename that to, for examplebombit becomes a little clearer:bomb(){ bomb | bomb& };bombThis defines a function that calls itself piped into a version of itself in a separate, background, process (that's what the
&does) and then calls that function. Calling itself means the function never ends (it's essentially a recursive version of an infinite loop) and the extra background process that is created each time it's called means that it just keeps exponentially creating new processes that don't exit and each of which infinitely forks off more processes until the OS runs out of resources (unless you useulimitto set per-session/per-user process limits - this may even be done by default on some distros these days, it's been a while since I looked)So does it actually hurt anything?
Thank you, this is the first time I've ever actually seen the fork bomb described in a way that makes sense. I knew what it did but I didn't understand how the input string caused it, it was effectively just a magic rune of crashing to me. This is a great explanation.
Casual here ,
It is a process that copies and splits itself until all the computer's processing power is used up, causing it to crash.
Test it at your own risk
Usually, you can restart without problems afterwards .
I did this 10 years ago on a Mint computer.
This is the fun part of your journey with Linux , you are the boss of your computer.
Sounds awful. Since I switched to Mint my computer has only crashed when I got out of hand with Blender, I can't see myself doing it on purpose.
When I switched to Mint mine just started smelling nicer.
Stop using gras
People do it as a stress test of their system. A goodly OS should be able to stop it before it crashes the system, otherwise it won't cause much damage (depends on what else you're doing when it crashes)
This is correct
It was a nice experience, part of the learning process, discover your limits and go beyond them, everything at your own pace.
Make sure you always have multiple external backups, check them for errors as well.
Currently I am reading up on off grid communication mechcore and reticulum
All my computer is for is drawing pictures, making noise and occasionally doing internet stuff that's too obnoxious to do from my phone. I don't game or code or torrent. Really mostly just Blender and PrusaSlicer.
it creates a process that makes copies of itself. then those copies make copies... until your computer runs out of resources and crashes
Ick.