Skip to main content

akkoma - Link to source

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 seirdy.one/notes/2022/10/26/pr…


Add a WebFinger endpoint

Keyoxide is a service that allows us to map a "user@domain" relationship to a list of account URIs. [WebFinger](https://webfinger.net/) is a W3C recommendation for mapping a "user@domain" relationship to a list of account URIs.
Codeberg.org
in reply to Seirdy

Seirdy
akkoma - Link to source
Seirdy
• •
phew that took a lotta delete-redrafts cuz i forgot that most servers/clients don’t support <dl>
Unknown parent

Keyoxide
mastodon - Link to source
Keyoxide
• •
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?
#webfinger @Seirdy
⇧