Notices by deutrino (deutrino@mstdn.io), page 22

I managed to extract these Mastodon federation API endpoint (filename, [endpoints]) tuples from the code. No idea if this is complete or what.

accounts_controller.rb:
show

follower_accounts_controller.rb:
index

following_accounts_controller.rb:
index

statuses_controller.rb:
activity
show

tags_controller.rb:
show

activitypub/collections_controller.rb:
show

activitypub/inboxes_controller.rb:
create

activitypub/outboxes_controller.rb:
show

I mean you'd think that there'd be SOME differentiation between activitypub vs other types of endpoints beyond 'format.json do'.

good god, man.

oh my god this code ><

@onethousandtwentyfour Okay, I think I figured out what I need to crack this nut - it's not specified in routes.rb but I think I know what I'm looking for now enough to get a skeleton of it into my brain / the gitlab

@onethousandtwentyfour Huh, okay, cool. Yeah I was at the stage where I was wondering if everything was channeled through the apparent endpoints defined in the Masto ActivityPub controllers and nothing else. Hm. Still need to figure out how to get a list of all potential server-to-server endpoint URLs but I'm a lot closer than I was an hour ago :)

@david Cool, this helps, thanks. In the meantime I've learned to grok Ruby enough to realize that half the methods I was looking at are private 😅

@onethousandtwentyfour gonna look at routes.rb again now that I can read Ruby/Rails a bit better than I could an hour ago. haha

@onethousandtwentyfour Okay, thanks so much, this is definitely helpful although I am still somewhat confused especially due to looking at the activitypub controllers in the Masto source.

Do you happen to know if Mastodon is using a standard set of endpoint URLs derived from the #ActivityPub spec, or did he just make endpoints up and ActivityPub mostly defines the what, not the how...? See what I'm asking? :x

@onethousandtwentyfour That's how instances talk to one another tho? It doesn't go thru (e.g.) instance.tld/activitypub/inboxes/..., instance.tld/activitypub/outboxes/... and so forth?

@david Okay, cool, thanks for that info! Note to self: look out for nested resources.

Is there any situation in which the methods in a #Rails subdirectory app/controllers/foo/bar.py would NOT have a 1:1 correspondence with the URLs relevant to that controller? #ReverseEngineering

@elomatreb Oh *that's* good to know - don't have Masto installed anywhere though. I'm just digging thru the code right now trying to document various endpoints so we have something vaguely resembling a spec to code to.

@elomatreb Ah yup. Got that in my list! Also there's the instance info endpoint.

Is there somebody online who knows the URL schema to Mastodon's federation API?

Is it just, roughly:

inboxes/create
inboxes/set_account
inboxes/body (etc..)
outboxes/show
outboxes/outbox_presenter
outboxes/set_statuses (etc..)
collections/show
collections/set_statuses
collections/scope_for_collection (etc..)

(I'm just taking those from method names in the #ActivityPub controllers in Mastodon... I don't know Ruby or Rails.) #mastodev

@akhy hmmm, that's good to know about! I'm running FB in a virtual machine on desktop and a wrapper app (Metal) on my phone. I did manage to get past the spam block though after enough humans friended me back and I started seeming normal, I guess.

reverse-engineering a Masto federation API spec is hard. #mastodev

I'm trying to make a new #Facebook account to communicate with friends who use the platform extensively and won't use anything else, but I keep getting caught in the spam trap and challenged with captchas and the like. I'm doing this in a virtual machine that's only used for this purpose - Firefox ESR, updated but otherwise bare of plugins, etc. Does anybody know pointers / tips & tricks to making a FB account without getting repeatedly blocked for verification? I need this to evade harassment.

@kaniini Thanks a lot for the tip - followed :) @dansup