Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.

If you’re a server admin, please defederate Meta’s domain “threads.net

If you don’t run your own server, please ask your server admin to defederate “threads.net”.

  • Lucia [she/her]@eviltoast.org
    link
    fedilink
    English
    arrow-up
    11
    ·
    11 months ago

    How will they force their unethical business model on you?

    Their ToS (another user already sent a link to it) says they will collect data of anyone interacting with users on their service.

    There’s this weird argument that our data is public so privacy violation is okay. But, even if it’s technically possible to collect and analyze data of fedizens doesn’t mean it’s okay to do. If it would become known that some of the existing instances do this they will be immediately defederated by everyone. But of course it’s different for Meta because they’re such a nice company!

    • Womble@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      11 months ago

      You don’t have privacy in public, that’s the difference between public and private. If meta wanted to they could scrape the entirety of the fediverse every weekend without anyone being federated with an instance of theirs. So that isnt a good reason for defederating.

      Fear of EEE is a more reasonable argument, but given that it can be done at any point I dont see any reason to do it pre-emptively rather than take a wait and see approach.

      • Lucia [she/her]@eviltoast.org
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        11 months ago

        You don’t have privacy in public, that’s the difference between public and private. If meta wanted to they could scrape the entirety of the fediverse every weekend without anyone being federated with an instance of theirs. So that isnt a good reason for defederating.

        I literally said that: “There’s this weird argument that our data is public so privacy violation is okay.”

        It doesn’t matter if it’s public, they use their server for data mining and we can prevent that. Someone may collect our data secretely but it doesn’t make more open approach to data mining any better or more ethical.

        given that it can be done at any point I dont see any reason to do it pre-emptively rather than take a wait and see approach.

        The longer users on your instance interact with content on Threads, the harder it will be to defederate (people will get angy about losing their content and their reach).

        • Womble@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          11 months ago

          My point was that you cant have your privacy violated in public as you don’t have privacy in public. That’s what being in public means, a place that isnt private. Being federated or not has zero impact on whether Meta can ingest all the public data they like from the fedivese because its all public.