• gravitas_deficiency@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    92
    ·
    11 hours ago

    As a lemming, this whole drama is categorical censorial bullshit, but also peak comedy because the fuckwad got caught and publicly called on the carpet

    As a software engineer, this is stupid implementation, because you can trivially make this a configurable blocklist of strings and regex. It never needed to even be an argument. Which of course means that it was never about the implementation.

    As an open source enthusiast, take the software engineer response, but add: and he’s intentionally pushing his (visibly fucked up and warped) worldview and values onto users, and he tried to obfuscate it to be sneaky. That falls in the realm of malware imo - as in, intentionally mutating the functionality of a project with a specific intent of impact on users, and then attempting to hide the evidence. And then he got called out on it, and got super butthurt, and rage quit the whole goddamn platform.

    TL;DR: Good fucking riddance.

    • Axolotl@feddit.it
      link
      fedilink
      arrow-up
      14
      ·
      8 hours ago

      He even tried to wash it off with “but there is a setting to disable it, just navigate 32 sub menus and click toxic mode” and never addressed the fact that his software would hide the shit behind a “technicall issue” excuse

      • chaogomu@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        8 hours ago

        Did anyone bother to check if that “toxic mode” even existed, or existed prior to the jackass getting caught?

        • gravitas_deficiency@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          12
          ·
          7 hours ago

          Tbh, doesn’t matter.

          Dude clearly designed it to be included in his releases in a difficult to detect fashion. That’s “malicious developer” behavior.

          In the context of OSS, you design <thing> to do <function>, and you set things up to allow users and implementers to customize it as they see fit and necessary. Intentionally hiding opt-out mechanism - let alone shipping with shit you want or need to opt out of is very much a big tech bullshit tactic, and OSS devs who do that are objectively caustic OSS devs. Dude tried to foist his views and sensibilities onto everyone who used his shit in a very, very sneaky fashion

          It’s correct and appropriate that he got blackballed from the community.

    • ZeroGravitas@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      34
      ·
      edit-2
      9 hours ago

      Hello there, fellow Culture enjoyer.

      The absolute cherry on top for me was the trigger: a good old-fashioned post upgrade debug session. Your TL;DR ++