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
@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]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:
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
[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
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
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]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
[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.
[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
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