this post was submitted on 13 May 2026
72 points (90.9% liked)

Ye Power Trippin' Bastards

1833 readers
367 users here now

This is a community in the spirit of "Am I The Asshole" where people can post their own bans from lemmy or reddit or whatever and get some feedback from others whether the ban was justified or not.

Sometimes one just wants to be able to challenge the arguments some mod made and this could be the place for that.


Posting Guidelines

All posts should follow this basic structure:

  1. Which mods/admins were being Power Tripping Bastards?
  2. What sanction did they impose (e.g. community ban, instance ban, removed comment)?
  3. Provide a screenshot of the relevant modlog entry (don’t de-obfuscate mod names).
  4. Provide a screenshot and explanation of the cause of the sanction (e.g. the post/comment that was removed, or got you banned).
  5. Explain why you think its unfair and how you would like the situation to be remedied.

Rules


Expect to receive feedback about your posts, they might even be negative.

Make sure you follow this instance's code of conduct. In other words we won't allow bellyaching about being sanctioned for hate speech or bigotry.

YPTB matrix channel: For real-time discussions about bastards or to appeal mod actions in YPTB itself.


Some acronyms you might see.


Relevant comms

founded 2 years ago
MODERATORS
 

Which mods/admins were being Power Tripping Bastards?
Rimu

What sanction did they impose (e.g. community ban, instance ban, removed comment)?

Kicking from all Matrix PieFed rooms

Explain why you think its unfair and how you would like the situation to be remedied.

Rimu has been manufacturing non-stop drama for weeks. He ignores multiple offers from multiple parties to de-escalate, and now he bans someone for trying to promote non-discriminatory language. He has also now cut off a PieFed admin from any and all support and ability to contribute to the software.

Oh and the real kicker ? Rimu did all this after his big grand post about how he is stepping back from drama and hiding away from users.

you are viewing a single comment's thread
view the rest of the comments
[–] scrubbles@poptalk.scrubbles.tech 4 points 20 hours ago (2 children)

You have a very rational way of seeing it, and I would have done the same thing. Only thing I'd say for the original asker is to be a bit more direct, they dance around it a bit, but that's a nitpik at most.

A story, I remember about 7 years ago I was asked to go through and rename every instance of "whitelist"/"blacklist" to "allowlist"/"denylist". I stand by that searching through the codebase and having me do that everywhere was a waste of time, it took me about a full week of time just to do that change with DB migrations and frontend updates and everything in just my chunk of code, I can't imagine how much time was spent company-wide. I found out it was actually pushed by the "People Department" as they called themselves then, and they did not care at all that it was in code only and not even visible to anyone. But I rolled my eyes and did it, it's just one of those things. I do purposely choose allowlist/denylist when writing new code because I understand it, but I also stand by it was asanine and meaningless to waste time and have me do all of them at once. A better mandate would have been "If you see whitelist/blacklist, you should now change it to allowlist/blocklist as you come across it, with teammates holding that bar in PRs. No modifications should be done without also updating the naming".

[–] curbstickle@anarchist.nexus 3 points 20 hours ago (1 children)

A better mandate would have been “If you see whitelist/blacklist, you should now change it to allowlist/blocklist as you come across it, with teammates holding that bar in PRs. No modifications should be done without also updating the naming”.

Yup! This is how I handled it, along with some other similar language changes in more industry specific language use cases. Only exceptions were user-facing dialogs. Surprise, surprise, everything that needed to be changed happened over the course of a few months anyway.

[–] scrubbles@poptalk.scrubbles.tech 3 points 20 hours ago (1 children)

Yup, and probably a lot less engineering time too since those who came across each one knew the details of what they were working on, and what the implications of the change would be. Vs what I had to do which was learn about each one, make sure I wasn't destroying something, making sure no one else depended on, repeat times like 30.

[–] curbstickle@anarchist.nexus 1 points 20 hours ago

Plus I didn't even have to justify the time involved either, since there was already a stakeholder for whatever changes needed to be made, it just went under the same hours as part of the required changes based on current standards.

Obviously community driven open source is a bit different (our code is open but still driven by business activity, so it didn't really come up otherwise except in rare scenarios), no need to justify hours or anything, so its even easier.

[–] mathemachristian@lemmy.ml 1 points 20 hours ago* (last edited 20 hours ago) (1 children)

Wait you got paid for that? How the fuck is it a waste of time then? Most of that time was wasted in exchange for a fraction of the value you produced

[–] scrubbles@poptalk.scrubbles.tech 1 points 20 hours ago

Oh of course, the entire engineering team was halted and it was mandated from the top. Everything stopped. Stupidest thing I've ever seen, I've never seen an HR department - sorry the "People Department" wield so much power. Completely stupid. They took no input on how we should do it properly.