petition: Defederate any instances that federates with threads proactivly , add threads.net on blocklists everywhere.

https://lemmy.ml/post/1784093

petition: Defederate any instances that federates with threads proactivly , add threads.net on blocklists everywhere. - Lemmy

I really want to nip threads in the bud. Besides blocking threads.net [http://threads.net] itself, defederate from any instances that do not. This is blatantly an EEE strategy and a united front is the only way to save what have been accomplished.

I’m all for individual users block Threads if they’d like to, but I think it’s a terrible idea for instance admins to make that decision for all of their users.

Personally, I don’t see why this is so controversial. I view it as a way to follow the celebs and organizations that would rather use threads, but from the comfort of Mastodon that is outside of Meta’s ecosystem.

ActivityPub and the Fediverse is designed to for natural selection to take place. So let it. The users that want to be part of the Fediverse are already here and won’t don’t leave based on what Meta does with Threads. Threads utilizing ActivityPub in the future justifies the means of the Fediverse more than anything else IMO. I despise Meta as much as the next person, but this is not the end of the Fediverse as we know it.