Together with our fellow administrators, based on some impact assessments, we have decided not to operate any preventative block against Threads, but I am not aware that we are still federated. I noticed that your instance is federated to Threads instead, but I don’t understand how this was possible. The strange thing is that, from your instance, it is still not possible to view those dozen Threads accounts that are currently “federable”. So I wanted to ask you: is there a way to force federation?

Thanks in advance for your feedback, sorry for the inconvenience and best wishes for a happy holiday!

you are viewing a single comment's thread
view the rest of the comments

[–] informapirata 3 points 9 months ago* (last edited 9 months ago) (4 children)

Now I understand: I thought that federating Threads was a deliberate choice, but it was probably an incidental phenomenon simply due to the large numbers managed by your instance.

Probably one of the ten Instagram executives who have a federated profile has tried to search for one of your contents. Or he found the message of a followed user who participated in one of your threads in his Timeline. Or they are simply experimenting with your instance...😁

I said the wrong thing here. Excuse me

~~In any case, there is at least one other Lemmy instance, probably for the same reason: it is an instance that handles quite large numbers anyway:~~ ~~https://sh.itjust.works/instances~~

EDIT: no it is not true: https://lemmy.world/comment/7949266

[–] kersploosh 14 points 9 months ago (3 children)

sh.itjust.works explicitly blocks Threads. They held a vote among the local users: https://sh.itjust.works/post/11308397

[–] informapirata 1 points 9 months ago (2 children)

Um... that's not what it looks like from the relevant page: https://sh.itjust.works/instances

[–] kersploosh 4 points 9 months ago (1 children)

It's in the "Blocked Instances" section, where it should be.

[–] informapirata 1 points 9 months ago

You're right, sorry 🤦‍♂️ 🙇‍♂️ : the federated instance was threads.ruin.io, not threads.net