Conversation

Notices

1. Emacsen (emacsen@emacsen.net)'s status on Thursday, 21-Feb-2019 18:07:42 UTC Emacsen

   • AndStatus
   • Yuri Volkov
   • thefaico
   • Christopher Allan Webber
   • Eliot Berriot
   • infinite love ⴳ

   @yvolk @andstatus @thefaico @trwnh @eliotberriot @cwebber Thanks for your thoughtful explanation, I'm not sure everyone mentioned here wants to be part of this discussion but it's an interesting one for me!

   I use the term "identities" specifically to reference the "id" property of the AP spec.

   And some of the technologies you mentioned (Webfinger in particular) are not part of AP, so I think it's important to mention that.
   [1/?]

   • AndStatus repeated this.
   • Yuri Volkov (yvolk@loadaverage.org)'s status on Thursday, 21-Feb-2019 18:33:46 UTC Yuri Volkov

     • thefaico
     • Christine Lemmer-Webber
     • Eliot Berriot
     @emacsen I mentioned WebFingerId not as a part of WebFinger protocol, but only as an artificially created identifier, helping to figure out the same actors via old-style (Twitter-like...) client APIs (which don't provide globally unique identifiers of actors (users...)).
     As we're currently are figuring out, how to use #ActivityPub C2S protocol in the real world :-) I see that WebfingerId isn't really needed in ActivityPub API: Actor's profile has enough information to know both username and hostname of an actor (what constitutes WebFingerId).
     I think that you will be interested to read our discussion on this here: https://github.com/andstatus/andstatus/issues/499
     
     @cwebber @thefaico @eliotberriot
     AndStatus repeated this.