this post was submitted on 26 Feb 2024
92 points (94.2% liked)
Fediverse
27398 readers
858 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
sh.itjust.works explicitly blocks Threads. They held a vote among the local users: https://sh.itjust.works/post/11308397
Um... that's not what it looks like from the relevant page: https://sh.itjust.works/instances
It's in the "Blocked Instances" section, where it should be.
You're right, sorry 🤦♂️ 🙇♂️ : the federated instance was threads.ruin.io, not threads.net