[tw2113_Slack_], deltab, [tantek], Kaja, saptaks, enpo, shoesNsocks, koddsson, jjuran, [snarfed], Seirdy, __minoru__shirae, KartikPrabhu and jeremy joined the channel
#tomlarkworthyMy overally goal is to deFAANG Firebase by swapping the Auth system with IndieAuth so Google never actually sees emails directly.
[Ana_Rodrigues], ShadowKyogre and [manton] joined the channel; ShadowKyogre left the channel
#[manton]I think IndieAuth will continue to work in Micro.blog even after the 10-day trial, it just won’t let you create a post. 🙂 But let me know and I’m happy to extend it.
#GWGtomlarkworthy: You could spin up a WordPress instance and use the IndieAuth plugin as well
koddsson, shoesNsocks1, shoesNsocks, sumner, [chrisaldrich], JankyDoodle, [jgmac1106], [tantek], KartikPrabhu, tru-is and ShadowKyogre joined the channel
#jackyjamietanna[m]: that's true (to a degree for me, I think unfamiliar / unrecognized ones should be either ignored silently or dropped [in a strict mode])
#jacky[schmarty]: I _think_ I agree b/c it doesn't actually _know_
#jackybut I think it's still okay for it to give a 'general' sense
#[schmarty]scopes are an agreement between the client and the server that actually handles the authorized request
#[schmarty]i don't think there's currently a way for an IndieAuth authorization or token server to actually know where an issued token can be expected to be used.
#[schmarty](like: does your IndieAuth endpoint know that you have a micropub endpoint? a micropub media endpoint? a microsub endpont? does it even need to?)
[tantek] joined the channel
#aaronpkas i'm going deeper into more of the OAuth specs, and also trying to rebuild everything in GNAP, i'm realizing that a lot of the problems and questions like this we have in IndieAuth have some overlap with other communities too, sometimes with already existing solutions
#[schmarty]to be clear i am not advocating for "solving" this at an auth server at the moment. so far the answers to my questions above have been "human coordination" and implementations have done well with that, haha. 😂
#jackybecause I'd love to link to something with more info (and maybe even sniff it out using MF2)
#aaronpkis glad oauth.net was the first result for GNAP :)
ShadowKyogre joined the channel
#jackyha yeah I suffixed it with 'oauth2' and it came up
[KevinMarks] joined the channel; ShadowKyogre left the channel
#[schmarty]ok finished up. Resource Indicators is kind of neat from a "where should this token be accepted?" perspective. however this spec doesn't contain anything that would enable those resources to define what scopes are possible or allowed or what they mean.
#jackyb/c now I wonder if it's possible to have some sort of descriptor link in a resource indicator
#jackyooh this is like literally saying "I want to do $SCOPE[] with $RESOURCE[]"
#jackytbh that can kinda address the thing you were mentioning [schmarty]
#jackylike if one of the resources is someone's micropub endpoint (and media) then it could be a stricter validation for things like `media` or `create|delete|update`
#jacky(as in using link-rel verification to confirm that those resources exist / are valid to the `me` associated with this token)
[chrisaldrich], ShadowKyogre, [aciccarello] and shoesNsocks joined the channel
#[schmarty]jacky: it could! but that would be some new spec where the auth server is discovering the endpoints it is allowed to make tokens for and then further discovering what scopes they support, etc.
#[schmarty]the resource indicators RFC supposes that all that is possible but doesn't give any mechanisms for doing it.
marinin[t] and [Rose] joined the channel
#marinin[t]hoping that I had not spammed webmention.rocks too much