• Axolotl@feddit.it
    link
    fedilink
    arrow-up
    26
    ·
    2 days 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

      • Axolotl@feddit.it
        link
        fedilink
        arrow-up
        1
        ·
        45 minutes ago

        Should’ve done it on reddit then, he would’ve got so many more people shitting on him

    • chaogomu@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 days 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
        18
        ·
        2 days 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.