I’m all for blocking Threads as an instance or user, but blocking instances that choose to federate with threads is going to leave a lot users who when Threads breaks its compatibility with Activity Pub with no social graph to keep them tethered to ActivityPub.

Threads can’t get the data we’re worried about it collecting from federation, they can only get it from you installing/using their site or their app. So don’t do that.

I think the difference between this EEE and say XMPPs EEE is Meta/facebook is widely seen as a cancerous entity that people who are already here aren’t going to want to use, and when they break compatibility few people are going to want to switch to their service as long as there’s still enough people here to talk to.

Not to downplay the threat of EEE, we need to remain vigilant. Our best defenses are preemptive defederation or shitposting how we never see ads.