[Rose], [Michael_Beckwit, KYZITEMELOS93[m], KartikPrabhu, [Tobias_Ljungstr, [grantcodes], jgmac1106, [jgmac1106], [schmarty] and testin joined the channel
@CCSDaytonOne of today’s projects is a big sound upgrade for this classic ride! The team at our WC store is installing a complete new system in this #Chevrolet #ElCamino, including an @AlpineUSA receiver, Alpine speakers, @JLAudio speakers, a JL Audio amplifier, and a JL Audio Microsub+! (twitter.com/_/status/1154813050492506113)
[snarfed]ah not so interesting after all. home page shows inbox/outbox, which implies it's a bridge, but https://twitter.activitypub.actor/schnarfed/json doesn't have inbox/outbox and says "You can't interact with it or follow it." ah well.
[jgarber]> Authorization endpoints verifying that a redirect_uri is allowed for use by a client MUST look for an exact match of the given redirect_uri in the request against the list of redirect_uris discovered after resolving any relative URLs.
[jgarber]The question is more in the vein of… Who’s advertising redirect URLs regardless of whether those URLs are on the client domain, a different domain, or are to native apps, etc. ?
[jgarber]More directly then: Do your clients/websites/what-have-you advertise/register valid redirect URLs using either a `Link` HTTP header or `<link>` elements?
aaronpkimagine instead of building a URL that you send the user to with the client_id and redirect_uri etc, instead you first post all that data to the auth server and get back a short string that you send the user to
aaronpkthere's a much bigger change to OAuth that's (probably) coming, which would also mean we'd be able to make IndieAuth a subset of OAuth instead of an extension
[jgarber]I’ll admit to remaining pretty confused by aspects of the OAuth/IndieAuth flow as I work on building an auth/token endpoint for my own use. So anything that cleans up the concepts and makes implementation simpler would be a win.
aaronpkAnyway I'm probably gonna try building out an IndieAuth server in the XYZ framework as a prototype, because I want to make sure whatever happens with that spec it's usable for us
[miklb]so my dilemma right now is I’m pretty much ready to switch back to jekyll/static but not sure what to use these days for indieauth/micropub. I’m excited to see the discussion kick back off in [grantcodes] repo so don’t want to paint myself into a corner.
[miklb]in the meantime, I’ve managed to lock myself out from .dev domains from my previous use of it locally. dnsmasq is off, all certs removed, nothing in /etc/hosts
[grantcodes][miklb] how would you want to handle your backend part? Use it to create markdown files in your repo or create a db that you can query at build time?
[miklb]maybe just because I have a whole bunch of content in a database right now that I won’t easily be able to get back outside of WordPress due to some design decisions.
[miklb]I can get the rest out as yaml front matter, but one major section of my IW stuff is still serialized. I tried to untangle it, but to no avail. Not a big deal for now, but just why I’m gun shy of another db at this time.
[miklb]but IndieKit is where I’m leaning simply because [Paul_Robert Lloyd] is actively working on it and jumping into the new conversation. Should help me get more familiar with the inner workings and help test, etc.
[miklb]I’d have to look again. I’d mentioned it before to GWG but didn’t seem like it was of interest. As I said, I was able to export all of my other post_meta to YAML front matter except a few big pieces of the IW plugins stuff. A little ironic though that there isn’t better data portability for an IndieWeb project.