I'm a simple nerd. I see someone actually reading the docs, I upvote.
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.
Arch Wiki has helped me many times even when I wasn't using Arch
I was referring to it's pages for years under ubuntu and it's constant helpfulness was certainly part of the reason that I switched to arch.
And it's not even the docs but the arch wiki, which has become an absolute treasure of concise-yet-extensive guides for running all manner of gnu/linux software, geared toward the modestly capable user.
I get what you mean, but the arch wiki is bacically the docs for arch...
And a lot of other distros, now that I think about it... :P
the arch wiki is so great, a systemd archwiki page helped me fix a sysvinit issue on devuan (had to convert some weird service into a sysvinit compatible one)
Hot plug permission rules. Don't forget to add yourself to dialout group.
Depends on the distro by the way. Not all use the same groups. Arch and its decedents have no dialout group for example.
Why? This is a great opportunity for me to learn a thing. Thanks!
Barely a Linux user but I did some troubleshooting recently and my basic understanding is that adding yourself to the dialout group lets your user access certain USB devices.
Serial devices too
I've never needed to do that. Hm.
It's not a group that exists in all distros, ymmv
I Googled it to double check and it's for serial devices.
I am fairly Linux savvy but udev isn't something I've gotten a handle on yet.
Can someone explain what's going on here to me?
I just wrote a post on how to use this to automatically disable/enable your laptop keyboard on plugging/unplugging your custom keyboard. Just one example.
In general, it allows you to set rules and automation about handling devices on the kernel level and comes with systemd (so most modern Linux distros have it by default, even Arch Linux)
https://fhoekstra.eu/posts/linux-disable-internal-laptop-keyboard-when-external-keyboard-plugged-in/
That’s the ArchLinux wiki, isn’t it?
Archwiki. What else?

I understand all of the words but none of the sentences