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
Elaborate please. I'm weighing installing Fedora for KDE. What kind of fucking around should I expect?
Just use the kiddy distro. We don't have time for your questions! 🧐
Also there are probably thirty actual decent KDE distributions. OpenSuSE is one of the very old ones, there are many others.
Eh it's kinda fine most of the time. But if you really don't have time to fix dependencies (via dnf) and constantly leave it for later, many broken things accumulate. It's usually fine (and usually works for at least a few years without problems, even on arch).
Edit: also the other comments.
Thanks. Just to clarify, by 'fixing dependencies' you mean upgrading the packages?
Fedora is a very early adopter of new technologies, often even earlier than Arch. They were the first to adopt PulseAudio, the first to use Wayland sessions by default, the first to drop Xorg, and will likely be the first to drop lib32 packages. Any issues that may arise from major upgrades or changes, you are most likely to be exposed to them on Fedora.
Got it, thanks.
Just try it for yourself in a VM and you will see.
That is an amazing non-answer. Very impressive in its uselessness. Good job.
Uh-huh. And how long do I need to run the VM before I run into an 'isn't stable' situation? Half a year, a year, more? Am I supposed to use the VM as my main machine during that time?
Just install it, try to install KDE (Gnome is the main desktop of Fedora), see if it works, if you like it, and if you can tolerate the slow ass package manager that is yum.
Should take you about 30 minutes; no need to be rude about it.
You can even try it in your browser if you think setting up a VM is too much time wasted: https://distrosea.com/de/start/fedora-44-kde/
Come on man. I know what KDE looks like. Running a VM for a bit won't help me learn what issues occur with Fedora sometimes.