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

    • @[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)”