Email or username:

Password:

Forgot your password?
Alex Gleason
Mastodon.social seems like it can talk to Threads fine, but nothing I do makes it work.

curl -H "accept: application/activity+json" -H "user-agent: http.rb/5.1.1 (Mastodon/4.2.2; +https://mastodon.social/)"; https://www.threads.net/ap/users/mosseri/

Even pretending to be Mastodon.social's user-agent 404s. I wonder if they have an IP whitelist.
7 comments
Alex Gleason
@mkljczk All Mastodon servers seem to have access to it, even widely blocked ones like https://gameliberty.club/web/@mosseri@threads.net

I wonder if it only worked yesterday and doesn't anymore. There's no other explanation for why my curl request doesn't work, unless I'm missing a header.
marcin mikołajczak
@alex Maybe they require signed requests, but then Pleroma with Mastodon user agent should work. But it doesn't
Alex Gleason
@mkljczk I'm trying to fetch it from a local Mastodon install and it's not working. This may be a waste of time. I wish we could at least see what the actor object is supposed to look like.
marcin mikołajczak
@alex If it's authorized fetch, then it won't work from a local install
Alex Gleason
@mkljczk bundle exec rails c
> ActivityPub::FetchRemoteActorService.new.call("https://www.threads.net/ap/users/mosseri/")

I'm trying this from a real Mastodon at animalliberation.social and it comes back nil.
Go Up