Skip to main content


Reply to Idea: Fediverse Profile UI component fed by Keyoxide back-end service by @humanetech

Many open standards can support profile hydration:
  • Ariadne: 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.
  • WebFinger: map an email-like identifier (an acct: URI) to a list of links.
  • vCard: upload 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:
  • Keyoxide profiles already contain h-card microformats, so we get that for free.
  • h-card microformats can have u-key properties, potentially triggering an Ariadne-based verification of accounts enumerated by the h-card.
  • h-card can map to vCard4
Depending on how keyoxide-web issue 141 goes, WebFinger could also indirectly give Keyoxide support.

POSSE note from https://seirdy.one/notes/2022/10/26/profile-hydration/
in reply to Seirdy

phew that took a lotta delete-redrafts cuz i forgot that most servers/clients don’t support <dl>
in reply to Seirdy

delighted to welcome you on the #SocialCoding forum, and thanks for adding to the idea.

The #WebFinger endpoint to @keyoxide is also an interesting one.
in reply to smallcircles (Humane Tech Now)

I really like @Seirdy 's idea too and should not be too hard to implement. My #webfinger knowledge is pretty limited but I assume we would add verified profiles to the "links" section?