I really want to nip threads in the bud. Besides blocking 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. Here is how Indivudals can do it on mastodont as an example to follow. https://hachyderm.io/@crowgirl/110663465238573628
I must genuinely ask? What does this accomplish, a lot of instances being split apart because one federates with meta and the other doesnt, its not like the meta posts are gonna make it to your instance if you defederate meta, so you are really just splitting the community over nothing. Privacy wise, activity pub is public, by design, so they can just already pull all the information it exposes, and likely do. And finally? How does this stop EEE?
I suppose if we burn our own community to the ground the moment we’re Embraced, there won’t be anything left for Meta to Extend or Extinguish.
Exactly.
Its not being Chicken Licking and freaking out that the sky is falling but we certainly dont need to play our hand this early in the game.
We know Meta is not a good faith actor. We know they will try to subsume or extinguish the fediverse if they cant control it but we dont need to go pissing our knickers and do the work for them.
I agree that defederation doesn’t solve the problem, the nice thing about federation is everything has an instance associated with it so as a user it is easy to know the source, and although we may not have easy solutions now, the data to provide instance blacklisting to clients is there. Personally I think the better way to neutralize threads would be a strict non-commercial license on all content served from an instance.