Conversation

Notices

1. AndStatus (andstatus@loadaverage.org)'s status on Thursday, 31-Jan-2019 17:20:04 UTC AndStatus

   • thefaico
   • :bunny:
   @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
   • AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 30-Jan-2019 15:55:20 UTC AndStatus

     • MMN-o ✅⃠
     • thefaico
     • :bunny:
     @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
   • AndStatus (andstatus@loadaverage.org)'s status on Thursday, 31-Jan-2019 04:36:31 UTC AndStatus

     in reply to

     • thefaico
     • :bunny:
     @kaniini  Thank you, after several attempts I figured out the correct full URL for the "whoami" API endpoint:
     https://pleroma.site/users/AndStatus/inbox - 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: "The inbox is discovered through the inbox property of an actor's profile".
     This is why the "whoami" call should be the same for every user, and not the "inbox" of a concrete user/actor.
     I think :-)
     
     This is "whoami" call where the authenticated Actor receives his/her profile information, including URLs of endpoints!
     
     ?!
   • AndStatus (andstatus@loadaverage.org)'s status on Thursday, 31-Jan-2019 15:59:37 UTC AndStatus

     • thefaico
     • Rysiekúr (old account)
     • kaniini
     • maryjane :fediverso:
     @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
   • :bunny: (kaniini@pleroma.site)'s status on Thursday, 31-Jan-2019 17:32:18 UTC :bunny:

     in reply to

     • thefaico
     • :bunny:
     @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.
     AndStatus repeated this.