Conversation

Notices

1. Emacsen (emacsen@emacsen.net)'s status on Saturday, 09-Feb-2019 14:01:20 JST Emacsen

   • Christopher Lemmer Webber
   • Eliot Berriot
   • infinite love ⴳ

   @trwnh @cwebber @eliotberriot @kity

   Maybe I misunderstand the issue but I think part of it is that right now people are okay with having N ActivityPub identities in a way that mirrors their proprietary service life. "Mastadon, PeerTube, Pixelfed" each on their own. But if you moved the bar the other way, to each of those being some sub-stream of your general AP identity, then you'd insist on a client (or c2s model) that was flexible enough to handle it.

   • AndStatus repeated this.
   • AndStatus (andstatus@loadaverage.org)'s status on Thursday, 21-Feb-2019 00:39:23 JST AndStatus

     • Christopher Lemmer Webber
     • Juanjo Faico
     • Eliot Berriot
     • infinite love ⴳ
     @emacsen #AndStatus Android client allows you to setup as many user accounts as you wish in several types of Social networks (#ActivityPub is in testing now). And it recognizes the same your Actor in different instaces, showing a combine view of one Actor via several networks, or a view of all your Actors...
     
     @eliotberriot @trwnh @kity @cwebber
   • Emacsen (emacsen@emacsen.net)'s status on Friday, 22-Feb-2019 03:07:42 JST Emacsen

     • AndStatus
     • Juanjo Faico
     • Eliot Berriot
     • infinite love ⴳ
     • Yuri Volkov
     • [MOVED] Christopher Webber

     @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 Friday, 22-Feb-2019 03:33:46 JST Yuri Volkov

     • Christopher Lemmer Webber
     • Juanjo Faico
     • 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.