13 years ago today: created #RelMeAuth with @progrium.com, to replace OpenID 1&2 for *reasons*
* modest proposal: authentication using domain as identity, rel=me link to OAuth profile with rel=me link back¹
* @progrium.com suggested RelMeAuth name²
* I agreed, and wrote up a draft algorithm³
All on the same day. A few months later I wrote it up as a draft spec:
* https://microformats.org/wiki/RelMeAuth (could use some updates)
More updates and discussion:
See those links for RelMeAuth implementations in:
* PHP, Python, Node, Ruby, Go
RelMeAuth is simpler for both publishers & parsers (consuming code) than OpenID.
There are now more sites that support RelMeAuth (and the complementary IndieAuth) than OpenID (which is largely abandoned⁴).
And today, @Github.com rolled out support for multiple rel=me profile links!⁵
This means you can now use @Github.com’s OAuth (and their multifactor login etc.) to authenticate as your own domain via RelMeAuth on even more services.
E.g. see my profile https://tantek.com/github (not a typo⁶). The left sidebar links to my personal site, Twitter, and https://micro.blog/t all with rel=me markup.
This is day 26 of #100DaysOfIndieWeb #100Days
← Day 25: https://tantek.com/2023/029/t1/indieweb-beyond-blogging
→ Day 27: https://tantek.com/2023/033/t1/twitter-api-log-in-web-sign-in-relmeauth
⁴ OpenID 1&2 were abandoned for OIDC (OpenID Connect), a supposed update/replacement, despite dropping the goal of domain as identity, the use-case for OpenID in the first place, so the #IndieWeb picked up that use-case with RelMeAuth & IndieAuth.