Fedi.Tips 🎄 (@[email protected])
mstdn.social
1. Meta/Facebook has a horrific track record on human rights: - https://www.amnesty.org.uk/press-releases/ethiopia-facebook-algorithms-contributed-human-rights-abuses-against-tigrayans - https://www.theguardian.com/technology/2021/dec/06/rohingya-sue-facebook-myanmar-genocide-us-uk-legal-action-social-media-violence - https://www.theverge.com/2018/7/18/17587080/mark-zuckerberg-holocaust-denial-kara-swisher-interview 2. Meta/Facebook is trying to join the Fediverse. We need to defederate them. 3. If you're a server admin, please defederate Meta's domain "threads.net" (here's how on Mastodon https://fedi.tips/how-to-defederate-fediblock-a-server-on-mastodon/) 4. If you don't run your own server, please ask your server admin to defederate "threads.net". Your admin is listed on your server website's About page.

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”.

  • @MaalusEnglish
    -32•11 months ago

    Best part of it is - it’s all paranoia. Fediverse will never get a sensible percentage of people if everything new gets blocked for no reason, or “because they’ll destroy Fediverse”.

      • @MaalusEnglish
        -24•11 months ago

        Yeah, because it is all “slippery slope” and paranoia. So what that they federate? How are they going to force developers to implement ads? How will they force their unethical business model on you?

          • @[email protected]English
            1•11 months ago

            Is there a way to technically deliver an unbroken user experience to a thread user without privacy issues?

            • NoodlesEnglish
              5•11 months ago

              Not really that I can think of, which is why I don’t think anyone should federate with them. I agree it’s instance operator and users choice but I feel like the default shouldn’t be “sign your privacy away, block them if you want to have privacy again (which you likely already lost some of from being federated with them)”

          • @WombleEnglish
            4•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.

              • @WombleEnglish
                1•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.

    • @[email protected]English
      -3•11 months ago

      Yep.

      But I gotta admit watching all these old cis straight white dudes get terrified of social media is at least quite entertaining!