@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.
108.162.237.23 - - [14/Dec/2023:20:04:42 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
172.69.71.14 - - [14/Dec/2023:20:04:57 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
172.69.71.147 - - [14/Dec/2023:20:04:59 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
108.162.237.23 - - [14/Dec/2023:20:04:42 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
172.69.71.14 - - [14/Dec/2023:20:04:57 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
172.69.71.147 - - [14/Dec/2023:20:04:59 +0000] "GET /internal/fetch HTTP/2.0" 200 823 "-" "facebookexternalua"
@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.