#social 2018-04-13

2018-04-13 UTC
JanKusanagi, cwebber2, xmpp-social, vasilakisfil and evanp joined the channel
#
evanp aaronpk: I talked to sandro, looks like we'll get the namespace docs up
#
evanp aaronpk: and when you have a moment, I have another question for you
#
evanp Actually I guess I could just ask and you'll see it when you get beeped
#
evanp I realized it's @596 which is early in your longitude
#
aaronpk Good morning!
#
evanp Ha ha
#
evanp Sorry about that
#
evanp Round planet :shrug:
#
aaronpk I usually get up pretty early :-)
#
evanp OK, quick Q
#
evanp For OAuth 1.0 I think there's a pattern where the server returns identity information with the access_token
#
evanp Like {"access_token": "...", "id": "https://twitter.com/evanpro"}
#
evanp Actually, I think Twitter does it the other way, providing a whoami endpoint
#
evanp I think the use case is that the end user provides an ID to the client, which is used to discover the OAuth endpoints...
#
evanp ...but they might make a mistake, or change their mind, and authenticate with another account
#
aaronpk Oh yea that's what OpenID Connect tries to solve
#
aaronpk But most OAuth APIs that don't do OIDC have a userinfo endpoint
#
aaronpk there isn't really a standard around it, people just do it
#
aaronpk that's also what IndieAuth solves, returning the "me" URL of the user who signed in along with the access token
#
aaronpk https://www.w3.org/TR/indieauth/#access-token-response
#
aaronpk (IndieAuth also solves the problem of dynamic client registration by using DNS as the registration which helps in decentralized use cases like this)
#
aaronpk Did I lose you evanp?
#
puckipedia hmm yeah, I kinda hit the above issue while writing Kroeg v0, I hard-coded the user ID in the url and just assume that's the user ID you get back
#
puckipedia originally I made it so you can choose what actor to log in as, but that didn't work because I had no idea how to figure out who that was lol
#
aaronpk The IndieAuth spec addresses that exact concern
#
aaronpk Some notes on that here: https://www.w3.org/TR/indieauth/#differing-user-profile-urls
jankusanagi_ joined the channel
#
evanp aaronpk: sorry, I drifted
#
evanp I'll take a look, thanks!
fr33domlover, evanp and githree joined the channel
#
@KevinBankston What would be the ideal format for social network data portability (especially re: Facebook)? JSON Activity Streams 2.0? Something else? Has anyone written extensively on this question? Or for popular audience? https://www.w3.org/TR/activitystreams-core/ @RossSchulman @CodingTrain @stamos @JoeBeOne (twitter.com/_/status/984893432589094912)
#
@davywtf ActivityPub is not only a nice approach to escaping the social network "walled gardens" but it also has one of the best W3 specs I've ever read: https://www.w3.org/TR/activitypub/ (twitter.com/_/status/984899895466315776)