Aaron Parecki

I just implemented this in webmention.io and indielogin.com. Here's the PR that adds support to indielogin.com as a client: https://github.com/aaronpk/indielogin.com/pull/117/files

I updated my IndieAuth server on aaronparecki.com to look for the JSON data as well. It's not open source so I can't link to the changes, but it was super...

I also started working on a spec that describes this discovery method as an OAuth extension: https://github.com/aaronpk/draft-parecki-oauth-client-id-metadata-document https://drafts.aaronpk.com/draft-parecki-oauth-client-id-metadata-document/draft-parecki-oauth-client-id-metadata-document.html Since this isn't actually anything unique to IndieAuth, other flavors of OAuth...

This has been updated in the latest published version of the spec! Thanks for the input everyone! https://indieauth.spec.indieweb.org/#client-information-discovery If you have an implementation of this, whether that's publishing the metadata...

So far no migration guide, tho I do still want to write that up. There is the [change log](https://indieauth.spec.indieweb.org/#change-log) in the spec which at least calls out the changes.

That's an interesting idea! I can certainly sympathize with the challenges of adding markup to sites that use CMSs like WordPress. There is already the option for setting HTTP headers...

oh don't get me wrong I'm excited about adding this as an option on the publisher side, but it does mean additional complexity as an IndieAuth client because now you...

This has come up in a number of OAuth/OIDC working group discussions as well. Technically the `access_token` response parameter is required, but many people have worked around this by returning...

This is the older language which might be confusing, but the link from the service back to the user's site is still important. It just doesn't have to have the...