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”.
If your users are subscribing to 10,000 accounts who spam so badly that it causes resource issues, that’s not a Threads issue, that’s an issue of who you allow to use your instance.
That is exactly how it works. If your users are abusing your instance, it’s on you as the instance owner to decide whether their usage is inline with your expectations as a host, or if they’re better served elsewhere.
If your users are subscribing to 10,000 accounts who spam so badly that it causes resource issues, that’s not a Threads issue, that’s an issue of who you allow to use your instance.
That’s not how it works.
That is exactly how it works. If your users are abusing your instance, it’s on you as the instance owner to decide whether their usage is inline with your expectations as a host, or if they’re better served elsewhere.