I’m pretty confused debugging Threads fediverse interoperability. Sending new posts to Threads returns 404 not found. Even just trying to grab an actor with curl
and Accept: application/activity+json
fails, for any user.

@dansup Thanks. Doesn’t appear that I’m being blocked. More testing, seems maybe 404 is returned sometimes for other errors. I am able to grab a profile with a signed request. Still digging.
Threads requires all fetches to be signed, and the signing actor AP needs to include inbox and outbox URLs, even if they aren’t wired up

I also noticed that when I use the Threads cross-post button for a one time share, it comes over looking like this:


@bryan I think this is a bug in the Threads app. It works on the web / desktop. Maybe I can work around it, though.

@johnspurlock.com Thanks for the tip! I do sign requests and have an inbox and outbox in the user profile, but the outbox returns nothing right now. I’ll fill that response in with more fields and see if it fixes anything.
hmm, maybe double-check your signing code? (mine’s below) iirc threads doesn’t return helpful statuses, just 404s if it doesn’t like anything
this includes the user-agent btw, I found I had to set it to ‘Mozilla/1.0’ instead of a browser ua when proxying on the server
github.com/skymethod/mi…
