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
Sorry for meeting such an asshole maintainer. I'd never do this, especially for someone who actually did the preparatory work to find the location of the bug.
Seriously that's an incredible bug report.
I've changed some of the details so it's not easily googlable because it's linked to my RL identity. But the concise description of the bug, reproduction steps, why I strongly suspect it's happening, and where I strongly suspect the fix needs to be made were all included.
The maintainer's comments are pretty much verbatim.
This happens every single time I try to file a good bug report, without exception. I suspect they see the woman's name on my account and assume I have no idea what I'm talking about?
Computer science used to be for women until men realised there was money in it, and now they act like women are too stupid to understand it.
I'm working on a major website migration right now, and was literally hashing things out with timestamps yesterday. If I had to deal with encountering a 24th/no 0th-hour bug, I'd call up the old dev and ask them how they avoid shitting on their loved ones while being such a giant asshole. Make me fucking convert the hours to a number so that I can subtract by one, and then convert it back to a timestamp. I know it's a simple solution, but I would have definitely first wasted hours trying to figure out why and which of my 50,000 posts was causing my migration to fail.
Point being, what you call a cosmetic error could singularly fuel my nightmares for a month. Shame on the maintainer for acting so indignant over what I now consider the kindest bug report of all time. I'm so grateful that users like you exist.
For real!
And then, is 20260124-24:59:30 the morning of the 24th, or the 25th? Who knows?
Yeah, I'd buy that reporter a beer or something.
I wish the ones I get were half as good.
Then stop writing such obscure bugs?
You can't tell them what to do! Submit a PR, if you've already figured it out
It's starting to go from bug report to peer review. if she made the fix too, it'd be a fucking pull request
EDIT : Fix'd pronoun
He?
I made an assumption and didn't see/realise their pronoun indicators. 🤷
Let's less assumptions next time and then less mistakes :3