fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-09-19 20:02:10 +00:00
Code Issues Projects Releases Wiki Activity

Clarify that h-card and RelMeAuth are separate concepts

Browse source
This commit is contained in:
Rohan Kumar 2022-10-26 20:07:42 -07:00
parent 33beea3eca
commit edfe941af5
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/notes/profile-hydration.md
View file

@ -11,16 +11,16 @@ replyAuthorURI: "https://mastodon.social/@humanetech"
Many open standards can support profile hydration:
Ariadne
: map an email identifier to supported verified accounts.
: Map an email identifier to supported verified accounts.
The IndieWeb
: map a webpage with `h-card` to any account, with less-robust reciprocal-link verification.
: Map a webpage with `h-card` to any account. This can pair with other forms of authentication, such as [RelMeAuth](https://microformats.org/wiki/RelMeAuth).
WebFinger
: map an email-like identifier (an `acct:` URI) to a list of links.
: Map an email-like identifier (an `acct:` URI) to a list of links.
vCard
: upload a vCard containing profile information, possibly with "share contact".
: Mpload a vCard containing profile information, possibly with "share contact".
I think `h-card`-based hydration is the best place to start. We can later add support for more options: