Recent searches
Search options
@aaronpk I read over your post and a bunch of related links. Really fascinating stuff!
From your post: “All it takes to turn your website into a FedCM-supported site is adding a single `<link>` tag to your home page.”
Can you expand on this? IndieAuth (mostly) requires two `<link>` elements for authorization and token endpoints. What would a singular `<link>` look like in this case?
@jgarber A few years ago we changed the IndieAuth spec to use a single link tag so that it's easier and also more flexible in the future. This is a good example of taking advantage of that flexibility too. https://indieauth.spec.indieweb.org/#indieauth-server-metadata
indieauth.spec.indieweb.orgIndieAuthIndieAuth is an identity layer on top of OAuth 2.0 [RFC6749], primarily used to obtain
an OAuth 2.0 Bearer Token [RFC6750] for use by [Micropub] clients. End-Users
and Clients are all represented by URLs. IndieAuth enables Clients to
verify the identity of an End-User, as well as to obtain an access
token that can be used to access resources under the control of the End-User.
@aaronpk Oh! That's right, I should've remembered that. I added that as an endpoint to indieweb-endpoints-ruby a while back.
Was up too late reading, up too early with the kids, and haven't yet had enough coffee. 