#microformats 2022-11-02
2022-11-02 UTC
ur5us and Gabe joined the channel
# 
@aardrian ↩️ “Could be” is different from “is”.
None do, AFAIK.
Other than some possible bespoke solutions for some novel edge cases?
But then use a `<div>` with a class. Or a `data-*` attribute. Or microformats for existing parsers. Etc. (twitter.com/_/status/1587645938809466880)
# @aardrian ↩️ `<section>` has no meaning to users.
Browsers expose it to AAPIs only when it has an accName.
If as a dev you want to parse it for something anyway, then do so. There is your use case.
But you might be better off using microformats.
Remember, I am talking about end users tho. (twitter.com/_/status/1587650954433888261)
ur5us, [marksuth], [marksuth]1, IWDiscordGateway and barnaby joined the channel
# 
@brunowinck ↩️ could it inspire how we deal with microformats?
I need so see examples (twitter.com/_/status/1587744727075618816)
# 
@jorgezaccaro ↩️ I haven't heard of that! This? http://microformats.org/ (twitter.com/_/status/1587746372299661312)
[KevinMarks], [KevinMarks]1, saptaks, omz13, [campegg], [manton], [manton]1, jacky, ur5us, [snarfed] and sivoais joined the channel
# @aardrian ↩️ Indeed, microformats, JSON+LD, RDFa, etc. are all my go-to if I want to address crawlers. Kinda nifty seeing Google treat my recipes differently when I did that. (twitter.com/_/status/1587921352043872257)
[timothy_chambe] and [manton] joined the channel