It does not work on any Pleroma servers yet. But I believe that is an unintentional compatibility issue. However some servers seem to be outright blocked.
Let me explain. Threads requires signed fetches. What that means is that every GET request to a threads.net resource needs to be cryptographically signed. Threads will then look up the signer and verify its signature.
The request to Threads contains a signature, with information about how to verify it. Threads will then verify it by fetching info from the origin server before returning the data.
You can see Threads fetching your own server by looking at the "facebookexternalua" user agent. Try this command on your server:
grep facebookexternalua /var/log/nginx/access.log
If you see logs there, that means Threads is attempting to verify your signatures and allow you to access their data.
On Gleasonator, I am seeing logs there. It is trying to let me establish a connection, even though it fails due to a bug in Pleroma or Threads. This means Gleasonator is not blocked.
However, on Spinster, and the Mostr Bridge, I have no requests from Threads at all, despite sending signed fetches. graf reports that Poast also isn't receiving any requests.
I do not believe they are operating on a whitelist. If so, it wouldn't make sense for Gleasonator and many other widely-blocked servers like gameliberty.club to be able to fetch from Threads.
So then I thought it may just be a caching issue, or a fluke on their end. But when I make a request from Gleasonator, I get the pingback from Threads within seconds. On Spinster and Mostr, there is no attempt being made at all.
So I am starting to think they may be blocking at the server-level already. And they are blocking Poast, Spinster, and the Mostr Bridge.
@alex I also see attempts to fetch instance actor in my log, but the last one was ~5 hours ago. Now when I make a signed request, threads.net doesn't react at all, even if I send a signed request as a different actor.
@alex >poast was haxxorz! >me: it's probably an svg exploit >it was an svg exploit!! >threads isn't federating >me: it's probably a GET http-sig >it was a GET http-sig!!!
@silverpill I am still getting recent requests from Threads, every time I fetch. This proves they didn't turn the service off. They're choosing to deny some requests, possibly by actor origin.
@Moon@raccoon@alex I was looking forward to it because we are one of few servers that can actually handle the load of Federating with something that large (even if it is a ghost town). shame if they did in fact block us
@alex So they went out of their way to block (probably) the least hostile non-masto instance because of the evil women on Spinster posting about their evil crafting projects and evil knitted sweaters and crocheted blankets. And don't forget about their evil cats who can smell you're male.
@alex I tried to fetch https://www.threads.net/ap/users/mosseri from my other instance public.mitra.social and received a pingback from facebookexternalua. Is it possible that they block mitra.social but not public.mitra.social? Seems unlikely. I think their federation client may simply give up after several unsuccessful federation attempts.
@silverpill I don't know why they would target mitra.social. Does mitra.social have any requests from their user-agent historically? I have 0 from servers that don't work, which means no attempts were ever made.
@alex What I just found out: Friendica does the requests with their system actor. That actor only has got an inbox, but no outbox. After I added the outbox to the profile, I was able to fetch a user.
@alex It's not a bug. Technically a system actor doesn't need an outbox. Also it is no required field according to the specification, if I remember correctly.
@alex Over night some posts from Threads (from Adam Mosseri) appeared on my system, so this seems to work fine.
One is a video where Adam Mosseri explains the launch in Europe and the steps towards the Fediverse. It appears as if he has got a deep knowledge of this whole topic. For example he made clear that the whole system is the Fediverse, the Protocol is ActivityPub and Mastodon is one of many applications in the Fediverse. Here he is already better than a lot of the Mastodon users of the Fediverse, who always call it "Mastodon".
I'm still not 100% where this will lead to and which motivation they drive. I don't think that their primary target is to dry out the Fediverse. They have got 100 million active users per month, the fediverse around 2. You don't invest such a lot time just for 2% gain.
Same is valid for this "they want our profile data" argument. They can gain some information about which user interacts with other users. But this doesn't help their ad business, since they cannot connect Fediverse accounts with IP addresses or cookies or any other tracking techniques.
By now I think that they want to avoid trouble via the EU because of their Digital Markets Act.
I'll say it: most of the people freaking out over the Threads federation right now are neurotic, paranoid, and are desperate to maintain their hugboxes and publicly posture as oppressed victims of a big tech company.