this post was submitted on 27 Oct 2025
145 points (100.0% liked)
196
4748 readers
2646 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 9 months ago
MODERATORS
Let me guess: then you had enough when the plugins kept breaking / Gnome kept crashing completely and taking all your current apps with it? And you were told to "just don't use Extensions"?
If Gnome was a company (thank god they aren't) the people who decided for gnome-shell to be both the compositor and window manager in a single process structure with extensions directly injecting code into this monolithic Achilles' heel would've been fired by now.
That's really the thing… any other desktop environment isn't just working better, but also better at failing. Neither a program nor extension / applet will take your whole compositor down unless you install KWin scripts in KDE or sth. Meanwhile on Gnome your whole damn GUI can crash and restart if there's an issue with something as simple as drag'n'drop. On KDE this would only take down plasmashell (which can restart independently), not everything.
Thank you for coming to my TED rant.
It's been years, so I can't say for certain, but I don't think I ran into that issue. Gnome was my first Linux DE, so I kinda figured that's how things were in Linux. I decided to give KDE a spin on Fedora since I was installing a completely new distro and it wouldn't hurt to try something else new there as well. There was no straw the broke the camel's back, just trying new things and realizing, "oh shit this is waaaaay better".
I've been using exclusively Fedora KDE and Fedora Gnome for a while now. I like both and so I use both, but have only had a bit of an issue with KDE resetting my configurations with updates. Right now I have just a taskbar in KDE and nothing else on the bar after it reset again after updating. It has happened a few times over the years and takes a lot of effort to set it all up again, details for things like weather and specific style choices. I realize my issues aren't everyone's, but just thought I would chime in.
Might just be a Fedora thing, it doesn't happen on Kubuntu.