Fediverse

28396 readers

336 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

[email protected]

About federation with Threads: how is it possible that lemmy.world is federated? (lemmy.world)

submitted 8 months ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

Hi everyone, I’m one of the administrators of the Lemmy feddit.it instance - my nick is @poliverso@[email protected]

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

[–] [email protected] 25 points 8 months ago* (last edited 8 months ago) (1 children)

It is odd that threads.net appears on our instances page, while the same is not true for other Lemmy instances which have not blocked Threads. Lemmy.world is federated with Threads by default simply because it is not on our instance block list. I do not believe our instance has done anything special to force a link with Threads. I mentioned it in our admin chat and will update this post if I learn anything.

However, even with threads.net listed on our instances page, Threads does not seem to work with Lemmy. I am able to search and view Mastodon user profiles from lemmy.world, but it does not work for any of the Threads test profiles.

Edit: The lemmy.world database has no records for a person on threads.net. Our best guess is that a Threads user tried to interact with lemmy.world. Perhaps the process got far enough for our instance to recognize threads.net and add it to our instances list, but not far enough to create a record of the user in our DB.

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago) (1 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

[–] [email protected] 14 points 8 months ago (1 children)

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

[–] [email protected] 1 points 8 months ago (1 children)

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

[–] [email protected] 4 points 8 months ago (1 children)

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

[–] [email protected] 1 points 8 months ago

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