I’ve checked the fedipact signatories, but they all seem to be lemmy instances.

  • the_thunder_god@kbin.social
    link
    fedilink
    arrow-up
    35
    ·
    1 year ago

    I disagree that the admin of an instance doesn’t have the right to moderate it how they wish. By joining the server you agree to let that admin control what content you see on your instance. That’s how instances work. It’s still on you to agree/disagree with the admin and how they run the server. That’s why other servers exist and you have the complete right to associate with who you wish, or even run your own instance and run it how you like.

    I do not agree with the people wanting to control other servers by trying to force defederating from threads. Independent admins running their own server is what the Fediverse is built upon.

    • Kichae@kbin.social
      link
      fedilink
      arrow-up
      13
      ·
      1 year ago

      This.

      The nature of the Fediverse is that if you don’t agree with your admin’s running of things, you can pick a new admin. Or become one yourself.

      The admin has every right to decide what their website interacts with.

    • eh@nerdbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      I do not agree with the people wanting to control other servers by trying to force defederating from threads. Independent admins running their own server is what the Fediverse is built upon.

      As long as authorized fetch is implemented (and correctly), intermediaries can’t “leak” messages out anyways. If Threads wanted to read the contents of a boost, they would have to ask your server for that, and your server can tell them to screw off.

      Does kbin or Lemmy implement authorized fetch? If they don’t they should start working on it. And consider enabling it by default. I know versions of Lemmy >= 0.18 can talk to GTS (which enforces AF) so there is partial support for it. And nobody runs 0.17 because of how inefficient it is, so that won’t be too big of a backwards incompatibility issue. No idea how it works on kbin land here, but it should be implemented ASAP if only so that any future enforcement won’t break backwards compatibility.