we shouldn't do anything.

Isn't the whole promise of the fediverse that whatever the policies of one instance are, that doesn't necessarily affect all the other instances, and each can do their own thing. If an instance doesn't want to accept traffic from threads, good for them. But to try to organize a fediverse-wide response to threads seems a whole lot like the centralization the fediverse is supposed to not be.

I run my own instance and am defederating immediately (whenever they start federating). I did also join the pact.
I'll evaluate their impact a month or so in and decide whether or not to refederate.

I acknowledge there's potential for a positive impact here, so I will give them a chance.

Fuck em. Burn this place to the ground before we dance with the devil.

I have already blocked threads on my household instance. I decided that I don't want to have to trust major instance admins to take the same things seriously that I do.

Another vote to defederate here.

Given that everything right now is just speculation - I say sit tight, observe what actually happens and respond appropriately if it does start to go wrong. Defederation is very easy, we can do it when we need to

Threads is exactly showing the biggest problem with anything Fediverse. It's simpler for the user so it will be accepted. The amount of people I've already seen join is huge compared to mastodon.

Here's Eugen Rotchko's thoughts.

https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/

threads will never federate.

What’s the DNS I need to block to never inadvertently get sent to anything Threads related?

There needs to be a Mozilla-like foundation that builds a competitive product platform for Fediverse that looks slick, is free of bugs, and matches any additional features that Threads might come up with