• rational_lib@lemmy.world
    link
    fedilink
    arrow-up
    68
    ·
    edit-2
    21 hours ago

    shutting out a significant portion of your community without seeking their input first isn’t a sensible move for such a foundational open source project.

    Ironic when X shuts out anyone who isn’t logged in and shuts out anyone who doesn’t pay for a blue checkmark from having visible replies.

    Having an X account isn’t consequence-free - if it becomes where updates occur, people have to sign up for an account and subject themselves to nazis everywhere and all manner of crypto spam just to see updates. And they have to pay Elon tribute to be heard in response. It’s crazy that anyone sees it as being friendly to users.

    • Ferk@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      10 hours ago

      Were they using Twitter to provide exclusive updates not available anywhere else?

      My impression from the post is that they are publishing the exact same updates in multiple locations, including mastodon at https://framapiaf.org/@debian …so just because they were publishing in that one extra site to make it accessible to a particular subset of people does not mean all other people were being shut off from receiving updates.

      However, I do agree with the move, but only because Debian being a FOSS initiative should stay away from proprietary platforms and promote FOSS.

        • Ferk@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          10 hours ago

          I don’t know enough detail about ATproto, but I wonder if it’s technically possible to block access to posts without also blocking federation. From what I’ve heard the functionality is more modular than Activitypub (content indexing being a separate service from content hosting) so I wouldn’t be surprised if it wasn’t possible.