Conversation:
Notices
-
@kaniini I see that you already have everything to add "/whoami" endpoint:
- authentication works, so you know an Actor, who makes a request.
- you should only return the Actor's "object", not a timeline. I already see that you do have that object inside a timeline...
Will wait, thank you.
@thefaico
-
@kaniini I'm testing client to server #ActivityPub implementation of #Pleroma So far I cannot even complete user authorization step and get the authenticated Actor's endpoints (whoami / verify credentials...) at #Pleroma , because I don't know URL of the API point, see https://github.com/andstatus/andstatus/issues/499#issuecomment-457942709
Could anybody help me?
@mmn
-
@kaniini Thank you, after several attempts I figured out the correct full URL for the "whoami" API endpoint: http://status.hackerposse.com/url/18321 - and I got JSON response. Will parse it and return to You to move further, if you don't mind :-) However, this URL, looking like an actor's inbox, is conceptually incorrect for the "whoami" call as even #ActivityPub spec says:…
-
@rysiek Maybe it's the right time to start building (or completing implementation of) #ActivityPub compatible client to server API and not waste time on improvements of Mastodon's custom API ?!
@dfeyer @kaniini @maryjane
-
@andstatus @thefaico
AP C2S is a low priority project for us right now (we are trying to ship 1.0), but I will see what I can do this weekend.