#microformats 2021-08-11

2021-08-11 UTC
#
[fluffy] Also there are many amazing mf2 parsers already and there’s not really any reason to DIY it
ur5us joined the channel
#
[tantek]1 having some additional depth in parsing libs/tools is probably a good thing
#
[fluffy] True. And I guess it’d be nice to have a Python library that doesn’t depend on BeautifulSoup.
jacky and aranjedeath joined the channel
#
[KevinMarks]1 you could do it with html5lib but the docs really suck
Seirdy, jeremycherfas, hendursa1, ur5us, ur5us_, [jgmac1106], sebbu, hendursaga, [manton], [jeremycherfas] and [jacky] joined the channel
#
[jacky] The parser's being written in Rust atm! I'm working on a patch for the one already existing but to meaningfully contribute to it, I needed to read the spec
#
[jacky] I think I managed to have it work in _at most_ two passes of the DOM
Seirdy joined the channel
#
[jacky] Interesting, does anyone know of parsers that _embed_ `microformats/tests` into the repo for checking? I'm doing that now via a sub-tree
angelo and KartikPrabhu joined the channel
#
[jacky] No mention of the <picture> tag at https://github.com/microformats/microformats2-parsing/issues?q=is%3Aissue+is%3Aopen+picture or https://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties, does anyone have ideas/thoughts on using mf2 on that?
KartikPrabhu, ur5us_ and [Emma_Humphries] joined the channel
#
[tantek]1 jacky, closest I see is https://github.com/microformats/microformats2-parsing/issues/7
#
Loqi [tantek] #7 Should u-* parsing special case img srcset?
#
[tantek]1 feel free to add to that issue, or if you think <picture> should be considered separately, open a new issue with similar structure to that one
#
[jacky] ah yes, the imfamous srcset
#
[jacky] I'll check it out
#
[jacky] hm okay
#
[jacky] I think I'm going to support `srcset` _first_ then consider how the `<picture>` will work
#
[tantek]1 sounds good! do you have opinions on *how* srcset should work from a publisher perspective?
#
[jacky] Hm. I think for me, I'd use that to produce the `<picture>` tag (for now) on my site but keeping an inline <img> that has all of the actual mf2 info for now
#
[jacky] if there isn't any, that might be a bit trickier but I think I can assume a 'default' from the dimensions known about the image
#
[jacky] (if that's what you're asking)
#
[tantek]1 I think the challenge has been so far figuring out what is the expected / desired publisher use of srcset and microformats, and then designing for that (with specific use-cases), rather than how *could* publishers use srcset and attempting to design something abstractly.
#
[jacky] I think the most prevalent one for me would be Microsub clients using the proper image for the viewport they have (even on native or mobile devices, having a lower setting could be used for a toggle to do a 'data saving' mode)
#
GWG I an interested in solving this