#microformats 2022-10-26

2022-10-26 UTC
[snarfed] and mikeputnam joined the channel
#
@henshaw ↩️ Microformats (twitter.com/_/status/1585079433626791936)
ur5us, m5zs7k, barnaby, gRegor, [pfefferle], [campegg], Saphire and [pfefferle]1 joined the channel
#
Seirdy bit confused about u-photo versus u-logo regarding avis. my profile photo looks intentionally abstract (https://seirdy.one/favicon.svg), so i wouldn't describe it as a "photo". but it's not a placeholder either.
#
[snarfed] yeah, the u-photo name is a bit misleading, it's for all images, not photograph specific. https://github.com/microformats/h-entry/issues/24#issuecomment-847782948
#
Loqi [chee] as @tantek mentioned on irc, this would be a great opportunity to say something like "still image or set of still images" so it's clear that "u-photo" is not just for literal photographs
jacky joined the channel
#
jacky that's a good point
#
gRegor That's an h-entry discussion, though still applies
#
gRegor With h-card I think of u-photo as "avatar", so whether it's a picture, drawing, or some stylized image representing you
#
gRegor Only time I've used u-logo is if it's an h-card for an organization.
#
gRegor When it's literally the company's logo.
#
gRegor I'm not sure if there's any consumers of h-card doing something different with those two?
#
jacky hmm not I
#
jacky hmmm
#
gRegor ?
#
jacky I think I misinterpreted the initial prompt about wanting to clarify u-photo (thus retracting my "that's a good point")
#
gRegor Seirdy, if you want that favicon to show up in your h-card, e.g. in your author information beside a post, I would recommend it be the h-card's u-photo
jacky and dckc joined the channel
#
Seirdy gRegor: yeah that's what I did. i bring this up bc i think Keyoxide uses u-logo
#
gRegor What's Keyoxide?
#
Seirdy it's a decentralized alternative to keybase that doesn't store user data
#
Seirdy basically your pgp key or signed text file contains a bunch of account identifiers; it then queries those accounts to verify them.
#
Seirdy and it generates a profile
#
gRegor Cool, didn't know they supported mf2. nice!
#
gRegor Yep, u-logo: https://php.microformats.io/?url=https%3A%2F%2Fkeyoxide.org%2F9f0048ac0b23301e1f77e994909f6bd6f80f485d
#
Loqi Yarmo Mackenbach
#
Seirdy if your key is distributed via WKD you just enter an email address and it spits out cryptographically-verified account information, like webfinger or rel-me.
#
Seirdy there was some discussion around interop with mf regarding rel-pgpkey and possibly defining new rels for identity proofs
#
Seirdy im most interested in their work on finding a way to distribute a signed text file with the simplicity of WKD because that way they could move from pgp to something else
#
Seirdy also, curious: we've got h-card, legacy hCard, vCard4, WebFinger, and now Ariadne (the spec that keyoxide implements) for distributing contact info. is there any prior art on interop between them?
#
Seirdy legacy hCard-vCard3 interop is already quite straightforward
#
Seirdy and keyoxide should map really easily to webfinger, since it literally takes an email and spits out a list of accounts.
#
Seirdy so we just need three things to work together: {webfinger,ariadne}-{hCard,vCard3}-{mf2}
#
Seirdy im thinking about this bc of https://discuss.coding.social/t/idea-fediverse-profile-ui-component-fed-by-keyoxide-back-end-service/144
#
Seirdy if there's a way to translate between the 5 aforementioned open standards that can fill the "machine-readable contact information for a person" use-case, then implementing just one way to "hydrate" an empty profile could open the door to hydrating a profile using any of the existing open standards.
#
Seirdy i think vCard should be the common denominator since everyone who has themselves in their phone's address book has one. just "share contact" to hydrate any profile.
#
[tantek] the vocabulary is fine, except for perhaps vCard3 vs vCard4 differences, which I'd recommend going with vCard4 which is then compatible with h-card
#
Seirdy cool, so we just need a way to convert Webfinger to a vCard4 subset.
#
Seirdy and profile hydration implementations won't have to "choose" which standard to implement; they can just start with vCard4 and maybe later add special features like verification for ariadne or mf2