aaronpkfor realm, I intentionally left it somewhat vague in the spec because I want to see what people end up doing with it. my plan for that was going to be to return either the URL of the person who can see the post, or a random string that maps to the URL
gRegorLoveOk, so seems it's fine to use the firebase/JWT lib and just JWT::encode('example.com')? Makes longer codes than I expected from the examples, but seems to work fine.
gRegorLoveWell, not sure I set up my token the "best" way, but it was an if/else: if POSTed 'code', perform all the auth checks, else validate Bearer token. I just added another condition at the beginning: if 'code' and 'grant_type=authorization_code'
aaronpkhm i just realized that according to OAuth 2.0, "client_id" is a required parameter of a token grant if there is no other client authentication happening (which in this case there isn't)
gRegorLoveI have a client_id in the micropub part of the token grant, though only because it was on /token_endpoint, not because I fully understand it :)
aaronpkclosest i found is this: https://mailarchive.ietf.org/arch/msg/oauth/STYsOy77_gknub-pOgO_mTg6cCA "By checking that the callback URI used to deliver the code is the same as the one used to initiate the flow, the authorization server can verify that the user who initiated the flow is the same one to authorize access and finish the flow."
tantekin other news, I have started sharing that URL with some gen 2 folks (per /generations) and asked for any/all feedback. If that's not the right URL (for someone using WordPress (self-hosted) and wanting more IndieWeb funcitonality (especially POSSE+backfeed), let me know!)
KevinMarks, AngeloGl1, singpolyma and AngeloGladding joined the channel