They're a keeper. Very stable and reliable.
this post was submitted on 24 Feb 2025
318 points (100.0% liked)
196
51 readers
69 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 month ago
MODERATORS
If your names are Debbie and Ian, it might just work!
Debian gang
confirmed lesbian
Debian gang
All I see is the hidden leaf village
"I'm switching to Ubuntu"
"So you finally snapped"
Maybe we can still achieve unity
They've got you there
who doesn't want a victim-blamer significant other with a superiority complex and a chair up an ivory tower they never get up from
what
In recent years, Debian maintainers have been acting with increasing disrespect toward upstream software maintainers and abusing their reputation of being a "stable distro" to shift blame for their bad decisions onto others.
The most significant example would be the orphaning of bcachefs-tools, during which Debian maintainers demonstrated outrageous incompetence in the way they package Rust libraries and a lack of willingness to make simple changes to their package manager (a way to have certain packages installed in multiple versions at once if the names of files inside those packages allow that to happen without conflicts) to accommodate for software whose library dependencies are at odds with those of other Debian packages. This incited an influx of harassment and bigotry towards the bcachefs-tools maintainers and the Rust community at large.
Another example that comes to mind is the KeePassXC fiasco, in which the build configuration for KeePassXC in its Debian package was modified to remove certain features, without any sort of prior communication or discussion with the KeePassXC team itself. One of the features removed by Debianers was the KeePassXC browser extension integration that helps users avoid exposing passwords to the clipboard when using the password manager, protecting them against clipboard grabbers. Because the KeePassXC team was not notified in advance, the settings menu of the password manager had no provisions for telling the user that specific features were disabled at compile time (the assumption being that only advanced users manually compiling KeePassXC would modify those settings), leading to their bug tracker being swarmed by frustrated and confused users of the Debian unstable branch who suddenly had the browser extension integration removed from their version of KeePassXC without a trace. This miscommunication put pressure on the KeePassXC team and misrepresented their software in the eyes of users, as Debian maintainers did not bother coordinating their changes with anyone. To add insult to injury, the Debianers then proceeded to scold the KeePassXC team on their issue tracker for supposedly having bad defaults, further escalating the purposeful breakage event into what came to most resemble bullying of upstream maintainers by Debian packagers.
When my son was 4 years old I took away his mattress and forced him to sleep on the floor every night.
If he did his chores, I closed his window.
If he got straight A's, I gave him a blanket.
If he got in a fight at school and won, I wouldn't force him to take his shower cold.
One day, he asked me,
"dad, why is that no matter how hard I work, I can't seem to earn a bed?"
I slapped him, first - every question carries a price - then responded,
"son, you can work as hard as you can in this world, it doesn't always mean you're going to get what you want."
Then I asked him,
"is there a bed in our house?"
He answered,
"yes, but it's yours, isn't it?"
I punched him again - for the question - then told him
"yes. If you want a bed, you need to fight me for it."
Our president is 80 years old.
The average age of our senate is 64 years old.
Young people expect the older generations to give them everything, they are never raised to fight for and take what they want, so they deserve nothing.
Waking up to my 7 year old with a blade held to my throat was the proudest I'd ever been.
As I slept on the floor, shivering that night in the cold (he also took my blanket and broke my window), I rested soundly, knowing I'd taught him well.