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”.
No, that’s just Lemmy. On Masto it blocks all interactions from users (including prohibiting them from following you and therefore fetching your posts).
Fair. But I’m on lemmy for discussion. I don’t want threads’ bobbleheaded userbase fucking up every discussion thread on lemmy. So I will stay on instances that have de-federated that shithole and urge other instances to do the same.
But they won’t. Seeing how little even the relatively federation-conscious Mastodonians interact with Lemmy, from Threads it will be close to zero (especially since the devs are very “careful” with federation and probably won’t display article-formatted posts anytime soon).
I’m not comfortable with assuming the dregs of Facebook will leave Lemmy alone. I’ll stick to instances that have defederated and I’ll actively block instances that don’t.
I’m not out here trying to stop you from being on federated instances or anyone else. But I will not personally support instances that allow that monster into the ecosystem.
You know that if you actively blocked the instances that are federated with Threads you wouldn’t have seen this post, right (lemmy.world/instances)? I’m also only active on instances that block Threads, but blocking those who don’t is an excessive measure.
That’s not how federation works. If you’re on an instance that doesn’t allow Threads, you won’t see them at all, even when viewing posts coming from other instances.
You’re confusing defederation with Lemmy’s instance blocking. Defederation means that none of a server’s content is federated. Lemmy’s new instance blocking feature, however, only blocks communities and not users.
We are on lemmy. So they are right in this context. I really couldn’t give a crap about anything like Twitter because I hate everything about that type of medium.
The thing is, you don’t really see anything from the Microblogging Fediverse around here at all, do you, so why would you from Threads? And Meta will only explicitly collect your data if you follow one of their accounts, which is impossible from Lemmy. So in a Lemmy context it is quite irrelevant.
No, that’s just Lemmy. On Masto it blocks all interactions from users (including prohibiting them from following you and therefore fetching your posts).
Fair. But I’m on lemmy for discussion. I don’t want threads’ bobbleheaded userbase fucking up every discussion thread on lemmy. So I will stay on instances that have de-federated that shithole and urge other instances to do the same.
But they won’t. Seeing how little even the relatively federation-conscious Mastodonians interact with Lemmy, from Threads it will be close to zero (especially since the devs are very “careful” with federation and probably won’t display article-formatted posts anytime soon).
I’m not comfortable with assuming the dregs of Facebook will leave Lemmy alone. I’ll stick to instances that have defederated and I’ll actively block instances that don’t.
I’m not out here trying to stop you from being on federated instances or anyone else. But I will not personally support instances that allow that monster into the ecosystem.
You know that if you actively blocked the instances that are federated with Threads you wouldn’t have seen this post, right (lemmy.world/instances)? I’m also only active on instances that block Threads, but blocking those who don’t is an excessive measure.
Like I said, I don’t care what others do. But for me the correct answer is to not interact with users from that platform.
When I start seeing threads users in .world lemmy comment sections I will block .world.
That’s not how federation works. If you’re on an instance that doesn’t allow Threads, you won’t see them at all, even when viewing posts coming from other instances.
I am given to understand that I will still see the comments from threads users on lemmy. Just not the posts from threads.
You’re confusing defederation with Lemmy’s instance blocking. Defederation means that none of a server’s content is federated. Lemmy’s new instance blocking feature, however, only blocks communities and not users.
We are on lemmy. So they are right in this context. I really couldn’t give a crap about anything like Twitter because I hate everything about that type of medium.
The thing is, you don’t really see anything from the Microblogging Fediverse around here at all, do you, so why would you from Threads? And Meta will only explicitly collect your data if you follow one of their accounts, which is impossible from Lemmy. So in a Lemmy context it is quite irrelevant.
Also,
I’m not ;)