• James R Kirk@startrek.website
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    14
    ·
    1 hour ago

    They posted an explanation in the tesseract community, but it boils down to they want the fediverse to succeed and replace reddit, but there is a contingent of toxic users that they feel is hindering that goal so they precompiled a list for new instance admins.

    It’s fully optional and can easily be disabled in the UI

    • Zombie@feddit.uk
      link
      fedilink
      arrow-up
      14
      ·
      45 minutes ago

      It is not fully optional. It was obfuscated and unremovable. That’s why the backlash has been so severe.

      Not to mention, why should a user interface make that decision? That’s up to individual server admins and their userbase.

      • Victor@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        24 minutes ago

        Fully agree on the weirdness that this would somehow be the concern of a frontend. Nah brh. Very strange.

      • OpenStars@discuss.online
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        19 minutes ago

        The author offers a lengthy explanation in their own words as to precisely why this was done. TLDR: people are free to stop using it, but he’s making these changes because he wants to offer this service on behalf of those who don’t enjoy all the toxicity here.

        • Zombie@feddit.uk
          link
          fedilink
          arrow-up
          4
          ·
          12 minutes ago

          Lmfao. I didn’t make it more than a few paragraphs because it’s written with the maturity of a 10 year old in a chocolate sausage museum.

          You can really tell they’re up for an honest and open conversation with the community, really trying to improve the Fediverse, with their locking of all comments.

          He’s clearly the toxic one and is projecting his issues onto hundreds of others.

    • OpenStars@discuss.online
      link
      fedilink
      English
      arrow-up
      4
      ·
      25 minutes ago

      THAT list is able to be disabled, though people are mad about its discoverability and transparency.

      The OTHER list, the smaller instance-level one, reportedly cannot be disabled, seemingly the only recourse for those instances on it are to use his fork of the code.

      This is from db0’s reporting, I have not attempted to confirm personally, but I would be happy to be corrected if need be.