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”.
However the serious problem with Kbin’s very lax approach is that it invites some really nasty people who will exploit it. I heard an admin say that a majority of the spam and CSAM attacks have come either from kbin.social or other kbin instances, and at the time it was made worse by a bug that prevented mod actions from federating from kbin, meaning the content stays up even after moderated on its home server. It wasn’t great.
However the serious problem with Kbin’s very lax approach is that it invites some really nasty people who will exploit it. I heard an admin say that a majority of the spam and CSAM attacks have come either from kbin.social or other kbin instances, and at the time it was made worse by a bug that prevented mod actions from federating from kbin, meaning the content stays up even after moderated on its home server. It wasn’t great.