#aaronpkis tempted to start using encrypted tokens everywhere so people aren't tempted to decode JWTs they shouldn't be
#gRegorLoveI'm refreshing my memory about the process; always get a bit confused when I first look at it again. The code in question is part of exchanging the authorization_code for the token
#gRegorLoveI thought it had to be decoded to verify the 'me' param and include it in the token
#aaronpkyour endpoints can talk to each other however they want, but if you ever get a token from elsewhere you won't need to decode it
tantek joined the channel
#aaronpkthe flip side of that answer is that if quill sends you an auth code that your auth endpoint issued, quill has no idea what that token is, it's just expecting a certain response. if you happen to be using JWTs, that's up to you, but quill has no idea
#gRegorLoveAha, it's actually my private webmention code interfering. The Micropub code isn't decoding JWT.
#gRegorLoveaaronpk: Sometimes after failing a test and then passing it, manually checking the third box, when I return to the list of tests, it still shows a red x. I run the test again and then it's green on the list of tests. Test 206 for example.
#aaronpkgRegorLove: do you have multiple tabs open or something?
#aaronpki'm always checked in to #indieweb IRC channels
#GWGaaronpk, I think all of my checkins may not be exciting. I usually only post locations I think someone other than me might care about
#sknebelbtw, I have poked around the code for chat.indieweb.org a bit. Did I miss it (not terribly familiar with structure of PHP projects), or is the bit sending new messages to the nginx-push-thingy not in there?
#sknebelthat I found, but not where I could check how it is (not) applied in the two different delivery channels (which seemed like the things compare for this)