Fellas, I think threads.net might be blocking some servers already.
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 flow looks something like this:
gleasonator.com -> GET threads.net/zuck (signed by /actor)
threads.net -> GET gleasonator.com/actor
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.
Interesting.
nostr:nevent1qqstpx2cmsxqvr4p7j07zc4l23aussxwa406c5tfuwtpqqrxhxkahsspz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qygrect9wz9829z5cre64nd870p22gu6jr2xj9fnth2ul5fywhqs07cpsgqqqqqqs25zdtl
Spin up a proxy on a different domain and see. It would be interesting if they were trying vacuum up fediverse content without sharing any of their own.
If course blackrock isn't gonna let poa.st users on to Facebook
There going to use it to populate threads app with more data and make it hard for ppl to pull from it, then when most ppl are on threads they are going to make incompatible changes to the protocol, trapping all threads users within threads #playbook #happensallthetime
This was called, months in advance.
nostr:nevent1qqstpx2cmsxqvr4p7j07zc4l23aussxwa406c5tfuwtpqqrxhxkahsspz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qygrect9wz9829z5cre64nd870p22gu6jr2xj9fnth2ul5fywhqs07cpsgqqqqqqs25zdtl
これは見えた
nostr:nevent1qqstpx2cmsxqvr4p7j07zc4l23aussxwa406c5tfuwtpqqrxhxkahsspr9mhxue69uhkummnw3ezuen9v35hvetjwdjju6ns9upzq7wzets3f63g4xq7w4vmflnc2jj8x5s63532v6a6h8azfr4cyrlkqvzqqqqqqytq2dks
Cool
nostr:nevent1qqstpx2cmsxqvr4p7j07zc4l23aussxwa406c5tfuwtpqqrxhxkahsspz4mhxue69uhkummnw3ezuerpw3sju6rpw4esygrect9wz9829z5cre64nd870p22gu6jr2xj9fnth2ul5fywhqs07cpsgqqqqqqs94skaz
For more stream diverting as their purpose maybe if I was not wrong. For the benefit from their sides, it doesn’t make sense, because the more they try to complicate the process the harder they serve their users, until one day more and more left them. 😮💨 👀