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.

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    2 days ago

    I would agree, but for them to get triggered by someone saying it is also stupid. Feel like I would have said “feel free to submit a PR”

    • curbstickle@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      13
      ·
      2 days ago

      I would have said “feel free to submit a PR”

      That was my thought.

      From me elsewhere:

      a change to code that would have some small positive benefit (for the people bothered by it) and no real negative other than, say, accepting a pr taking a few moments of time?

      I honestly wouldn’t have even read the original request as anything other than “Hey I’m bringing this up before I make these super simple changes and a pr, cool?”

      Which, to me, is just open source friendly chat and a way to say “If you were going to make a change here I won’t waste my time submitting on this” or “Maybe you’d want some more word options so I don’t waste anyone’s time”. The reaction is way different than what makes sense to me.

      • Scrubbles@poptalk.scrubbles.tech
        link
        fedilink
        English
        arrow-up
        7
        ·
        2 days ago

        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
          link
          fedilink
          English
          arrow-up
          6
          ·
          2 days ago

          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
            link
            fedilink
            English
            arrow-up
            4
            ·
            2 days ago

            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
              link
              fedilink
              English
              arrow-up
              4
              ·
              2 days 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[he]@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          2 days ago

          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
            link
            fedilink
            English
            arrow-up
            3
            ·
            2 days 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.