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”.
Lemmy 0.19’s instance blocking does not filter users, only communities, in addition it does not solve the problems of content polution because it does not limit interaction from blocked malicious users in any way, just hides them (it only really works under the assumption that they’re not malicious users and the blocker is just throwing a fit). For these reasons it is not and cannot be seen as an a replacement to defederation.
Also as I already said users are 100% free to decide, they decide by choosing their instances. If you don’t like it you’re free to host your own or move to a more open protocol like Nostr. The idea of federation was built around the idea of communicating with certain instances and blocking others, not about users individually choosing the servers they connect with, Some servers do operate democratically but in the end the fediverse is designed around servers so servers have every right to choose.
Also I’d like to address the “defederation will kill the fediverse” claims I’ve seen floating around. It won’t in fact it’s a dedicated feature of activitypub and has been in use since forever, instances are able to block ones that go against their values either due to the way those instances are operated or the users they allow on them. This is how it’s worked since the beginning and almost certainly how it will continue. Some users don’t like this and believe that they should be able to access stuff no matter what, failing to realize that they do not own the server their account is hosted on, accessing content on other servers via activitypub requires the content be copied over to your home server, and if the admins don’t want that they can block that server, you don’t really have a say in it because it isn’t your server. So either host your own where you do own it, or move to a more open protocol which exist for the purpose of user freedom and anti-censorship.
Lemmy 0.19’s instance blocking does not filter users, only communities, in addition it does not solve the problems of content polution because it does not limit interaction from blocked malicious users in any way, just hides them (it only really works under the assumption that they’re not malicious users and the blocker is just throwing a fit). For these reasons it is not and cannot be seen as an a replacement to defederation.
Also as I already said users are 100% free to decide, they decide by choosing their instances. If you don’t like it you’re free to host your own or move to a more open protocol like Nostr. The idea of federation was built around the idea of communicating with certain instances and blocking others, not about users individually choosing the servers they connect with, Some servers do operate democratically but in the end the fediverse is designed around servers so servers have every right to choose.
Also I’d like to address the “defederation will kill the fediverse” claims I’ve seen floating around. It won’t in fact it’s a dedicated feature of activitypub and has been in use since forever, instances are able to block ones that go against their values either due to the way those instances are operated or the users they allow on them. This is how it’s worked since the beginning and almost certainly how it will continue. Some users don’t like this and believe that they should be able to access stuff no matter what, failing to realize that they do not own the server their account is hosted on, accessing content on other servers via activitypub requires the content be copied over to your home server, and if the admins don’t want that they can block that server, you don’t really have a say in it because it isn’t your server. So either host your own where you do own it, or move to a more open protocol which exist for the purpose of user freedom and anti-censorship.