MOVED TO FediPact@cyberpunk.lol @FediPact@tech.lgbtbeen seeing a lotta posts lately that're like "OMFG THESE FEDIPACT PEOPLE ARE BLOCKING EVERY INSTANCE THAT FEDERATES WITH THREADS"
no. we're not. nothing anywhere on https://fedipact.online says anything about that lmao
i have seen exactly one example of someone planning to do this, and that's it
it's being blown ridiculously outta proportion
@FediPact
If it is the same example I saw, it's not even an instance but a user. 
I have said this in the past, so you may be referring to me. And I stand behind that: I don't "plan" for us to do this; Rather, I think we'll be forced to do this eventually, one way or another.
Threads is so large that most threads will have posts from Threads users woven in. Fedipact people won't be able to either see or interact (depending on policy) with those posts and it will be frustrating, bordering on unusable.
@maltimore
No, I wasn't reffering to you. Seems there at least two people who plan to do this.
About threads on federated instances I guess that will be the same as it is now. If someone on an instance that has been domain blocked on your side writes in the same thread you will not see it and that account can not respond to you. If Authorized Fetch is activated on your instance the other account won't even see what you write.
@Yuvalne@433.world@FediPact
and also, instance admins definitely have the right to choose to only federate with fedipact instances. toxic trends from Threads can easily infect the Fediverse, and people have the right to want to avoid that.
federating only with fedipact instances isn't more illegitimate than any other form of allowlist federation - that is to say it is perfectly fine.