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”.
threatening to harvest our conversations without our fucking permission,
Public posts on social media are well public. There’s literally nothing that stops them from reading your posts without federation, and federation does very little to change that in a meaningful way.
or using Microsoft’s tactic of “embrace and extend” to destroy the competition
By what, adding features to Threads that make users prefer it over other ActivityPub implementations? The worst case here is that Meta federates, then does something that breaks federation and their users don’t jump ship to another instance but stick with the Meta product?
Anyone can implement ActivityPub. We have no problem with that.
So long as they aren’t a giant corp you personally see as especially evil, then if they implement ActivityPub they need to be blocked as globally as possible?
Public posts on social media are well public. There’s literally nothing that stops them from reading your posts without federation, and federation does very little to change that in a meaningful way.
By what, adding features to Threads that make users prefer it over other ActivityPub implementations? The worst case here is that Meta federates, then does something that breaks federation and their users don’t jump ship to another instance but stick with the Meta product?
So long as they aren’t a giant corp you personally see as especially evil, then if they implement ActivityPub they need to be blocked as globally as possible?