Someone (later called a hacker) said Threads was still on the Linked Instances column, not the Blocked Instances column.
To be clear, I did not call that person that said that a hacker.
What I said is that when the hacker screwed with our settings due to the XSS vulnerability, they added threads to the allow list instead of the blocklist
I have this but I don’t see Threads on there.
Please edit that link out of your post. The tool you have linked to is developed by kiwifarms, and it has no place here.
You can find our list of connected and blocked instances via the "Instances" link at the bottom of every page.
If Threads is defederated, does that mean Meta/Facebook are as well?
No, because threads is the only meta application that is going to federate with the fediverse. If other meta services announce plans to connect to the fediverse whilst hosting hate groups, we will defederate from them too
Threads has not yet added ActivityPub, so right now there is nothing to defederate from. And ActivityPub support is “a long way off” according to Meta.
We could preemptively defederate from threads.net, but we can’t even be sure what domain Meta will eventually use for ActivityPub—they could use threads.social or something for all we know. So preemptively defederating is a gesture.
So to answer your question, it doesn’t matter right now whether threads.net is in a linked or blocked column. They aren’t on the fediverse yet. Nothing is flowing from them because they have no ActivityPub support.
We could preemptively defederate from threads.net, but we can’t even be sure what domain Meta will eventually use for ActivityPub—they could use threads.social or something for all we know. So preemptively defederating is a gesture.
FYI, this thread was posted in the Meta community for Blåhaj Lemmy, so the OP was asking about our specific defederation policy. And we do defederate from threads, because even though it's not yet federating, it will be at some point, and I saw no point in holding off