#jackyonamacbookoy, another moment where I'm feeling that wiki is good for history but _not_ for capturing dev information tbh
#jackyonamacbooklike I was wondering what's the accepted set of params for `q=source` and the only one "approved" is `url`. Which is clear(ish) on the Wiki (I'm editing now) but the other options should be some how highlighted
#Loqijacky has 30 karma in this channel over the last year (113 in all channels)
#aaronpkThat's the opposite of what it normally is
#aaronpkand why we started moving discussions to github
KartikPrabhu, gRegorLove, nickodd, [tantek], [jeremycherfas], [chrisaldrich], [KevinMarks], tinfoil-hat, moppy and [Sadik_Shahadu] joined the channel
#@AndreJaenisch↩️ Personally, I'd like to see more people getting a homepage (and domain) of their own and interact with each other via Webmention, i.e. a revitalisation of federation of content.
The WWW has the advantage of being open.
Embracing semantics allow for building a knowledge graph. (twitter.com/_/status/1284491416631160832)
ThatSummer[m] joined the channel
#ThatSummer[m]Ah, I've made it in. 🙂 Matrix is a bit weird about finding IRC chat rooms.
#ThatSummer[m]So I'm making a GET request to an authorization endpoint with query params. In this case, the auth endpoint is: indieauth.com/auth. An example of the full request below:
#aaronpkthis is a link you'd redirect the user to in their browser, so the error message is printed on the page there
#ThatSummer[m]Oh I see! I was working on the server side for this (and I thought that was the correct approach) but let me revisit things in that case.
#ThatSummer[m]Opening that link the browser says redirect_uri isn't specified... which is correct as I had specified it as "redirect_id" :(
nickodd, [snarfed], [tb] and [fluffy] joined the channel
#GWGIf I have an array of key value pairs, and the keys are delimiter separated... example key being a:b:c...and I want to turn it into a multidimensional array, what is the most efficient way to do so in PHP? I feel like I could optimize this somehow
#aaronpk(you can choose which to use, but it's not actually doing the indieauth spec)
#[tb]Ah gotcha. Spelunking through the source for omniauth-indieauth, it looks like it's actually _mostly_ compatible for the request/callback phases, other than the hard-coded `/sign-in` path segment here in the initial request—which looks from the IndieLogin docs like it would just need to be `/auth` instead
#aaronpki don't do much ruby stuff anymore so i'm happy to turn it over
#aaronpkit needs some updates to discover the user's authorization endpoint
[tw2113] joined the channel
#[tb]Aha — well maybe I'll take a stab at it here once I get a bit further along on this project then!
#aaronpk[snarfed] would you consider adding support for webmention status feedback in bridgy? where you'd be able to show the final status of the webmention that the receiver reports? happy to negotiate what the details of that would actually look like
#aaronpkbut curious if you'd be interested in exploring it
#aaronpkthe problem is right now all bridgy can show is that sending the webmention worked, which doesn't actually tell the user whether it was successful
#[snarfed]also do we have enough consistency in the wild with wm receivers returning 200 vs 201 vs 202 correctly semantically?
#[snarfed]the q's in my mind are more around, what's the behavior range of wm receivers in the wild, how often will we get false positives/negatives/breakages from this, etc
#aaronpki'm not eager to make bridgy do yet more polling, so i'd definitely be happy to do a push-based approach instead
#[snarfed]do we have a de facto standard for even detecting a status page? 202 + Location response header?
#aaronpkin which case the http response code isn't really relevant to this
#aaronpkbridgy could send another url along with source & target, and webmention.io could post back to that when it's done
#[snarfed]eh yeah but polling a Location header is at least somewhat converging on a de facto standard
#[snarfed]i'm especially reluctant to make up anything new or bridgy-specific
#[snarfed]or seems like a websub candidate? guess the tradeoff is, websub is standard, but it's heavier than we need here...but it's standard...but... 😁
#ZegnatI feel like the trickiest part with status pages is whether you go machine or human first. A webmention sender built into a CMS may want some machine readable answer. But if a human used a web form to submit a comment URL on a blog post they would prefer to get HTML.
#aaronpkZegnat: yes and i think webmention.io status pages support conneg for that
#aaronpkbridgy publish returns the resulting silo URL in the Location header, which looks like a webmention status page
#Zegnatconneg++ (although I may be in the minority liking it :P )
#[snarfed]also excuse me patting myself on the back here to say, thank god, it doesn't happen, but answering questions like "what fraction of the community is on wm.io" as data to help us make design decisions is *exactly* why i built indiemap
#aaronpkis the status code relevant here tho? isn't the presence of the Location header enough?
#aaronpklike if someone returns a Location header but also sends 202 instead of 201, that's not valid HTTP but it'd still be fine to treat the Location header as a webmention status URL
#aaronpkok of the status URLs i have logged in telegraph, they are only from either webmention.io, indienews, bridgy publish, lighthouse, and then there are three websites that return the target url in the location header for some reason