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”.
I remember what the standardising committee did to XMPP: users wanted to share photos, send files, and make audio/video calls; XMPP said “we’re not going to standardize that, but each application can use its own extensions”… then it all went to hell.
I agree, but one can ascribe that to corporate influence (or wish to win corporate love) too. Such a decision on first glance makes sense for using XMPP as a constructor for various system integration tasks, or for making proprietary services using it inside (not retroactively, but well).
I remember what the standardising committee did to XMPP: users wanted to share photos, send files, and make audio/video calls; XMPP said “we’re not going to standardize that, but each application can use its own extensions”… then it all went to hell.
I agree, but one can ascribe that to corporate influence (or wish to win corporate love) too. Such a decision on first glance makes sense for using XMPP as a constructor for various system integration tasks, or for making proprietary services using it inside (not retroactively, but well).