#microformats 2024-11-25

2024-11-25 UTC
[morganm], srijan, xgpt, Burke, jimw2, [qubyte], jimw3, ancarda, capjamesg, greenfork, mebious, gRegor, sebbu, eitilt, lazcorp, [Murray] and [benji] joined the channel
#
lazcorp Is there an accepted order of priority for posts (https://indieweb.org/posts)?
#
lazcorp For example, if I REPLY to someone else's post with a PHOTO, does the 'u-in-reply-to' element go around the 'u-photo' element?
#
lazcorp h-entry
#
lazcorp --u-in-reply-to
#
lazcorp ----u-photo
#
lazcorp (like that?)
[mattl] joined the channel
#
lazcorp Hmm, actually ignore that - I think it's a flatter format - the 'u-in-reply-to' goes on an <a href></a>, then the next element (not inside the <a>) would be an <img> with 'u-photo'
#
[schmarty] it's more like a post (h-entry) _has_ those elements. the u-in-reply-to link and the u-photo are siblings.
#
[schmarty] yep yep
#
lazcorp (me, overthinking simple implementation standards since I was born)
#
lazcorp thanks for confirming, [schmarty]
#
lazcorp [schmarty] ++
#
Loqi [schmarty] has 1 karma in this channel over the last year (26 in all channels)
#
[schmarty] lazcorp++ welcome to the party, haha, i think about microformats all too often and i still find them confusing a lot of the time.
#
Loqi lazcorp has 1 karma in this channel over the last year (14 in all channels)
#
lazcorp Some more stupid questions:
#
lazcorp With regards to https://indieweb.org/photo and https://indieweb.org/multi-photo
#
lazcorp Is there any difference in mark-up (apart from a multi-photo post has multiple <img class="u-photo"...> elements
[snarfed] joined the channel
#
[snarfed] that's it, https://indieweb.org/multi-photo#How_to_publish
#
lazcorp Thanks, [snarfed] - photo and multi-photo having different pages on the wiki confused me (very easily done)
#
lazcorp [snarfed] ++
#
Loqi [snarfed] has 1 karma in this channel over the last year (94 in all channels)
#
lazcorp Final bonus question: if I want to replicate a common social media post type where I @ someone (but not in reply to a specific post of theirs - more like "@someone - have you finished your posts implementation yet") then it is NOT a reply, then how do I do that?
#
lazcorp Is it just a basic note that starts with a person-tag https://indieweb.org/person-tag
#
lazcorp or is the person-tag specifically for tagging people who are in a photo you have posted?
#
[snarfed] I think the latter
#
[snarfed] I think you're describing just a "mention"
#
[snarfed] https://indieweb.org/person_mention
#
lazcorp Aha - and yes, there's an example on that page linking to Tantek's notes where he does something similar - http://tantek.com/2017/345/t1/aaronpk-paid-thanks
#
lazcorp There's no specific microformat class on the link to Aaron at the beginning
#
lazcorp if a person then replies to a person mention, then it becomes a REPLY to the URL of my original post (and if I reply to that then I REPLY to the URL of their response to me)
#
lazcorp Or to put it another way, the intiating message if a person mention where the URL is the addressee's homepage. Subsequent messages in that 'thread' are u-in-reply-to replies to the URL of the previous message in the thread
[juliaro] joined the channel
#
gRegor scrollback: the mf2 properties are parsed as siblings even if they're published nested. E.g. we've seen `.h-entry > .e-content > .u-photo`. That parse still ends up with a `content` property and a `photo` property. Though it also ends up with the HTML for the photo duplicated in the `content`, which is probably not intended.
#
gRegor I think that example happens enough that Monocle (or maybe Xray?) special cases it to remove the duplicate photo in the parsed result
#
gRegor I don't think issues like that arise specifically with photo replies, though. E.g. both these seem to parse as expected: https://php.microformats.io/?id=20241125223711676
#
gRegor More real world examples on https://indieweb.org/photo_reply
#
gRegor Just added a minimal "How to markup" on that^, updates welcome
#
gRegor I've occasionally, intentionally used that nesting behavior, like including a `p-summary` around some text that's also in the `e-content`, so I don't have to repeat the text.