#microformats 2024-10-14
2024-10-14 UTC
[pfefferle] joined the channel
#
[pfefferle] I would love to have your feedback on this: https://github.com/pfefferle/wordpress-webmention/issues/492

#
[pfefferle] how do you handle nested microformats that are not enclosed in a property

[Murray] joined the channel
#
[pfefferle] yes

#
[pfefferle] kind of

#
[pfefferle] it is like h-entry inside of h-feed

#
[pfefferle] but is h-entry inside of h-entry this by the spec? and do we want to support it as reply context?

#
[pfefferle] I think it is using h-entry as a more complex link!?!

amiga_mike joined the channel
#
[pfefferle] that's why I ask: do we think that this should be supported or so we only support if the h-entry/h-cite is encapsulated in an attribute (u-repost-of, -u-in-reply-to, ...)

#
Loqi explore the possibility of expanding metaformats legacy parsing rules to include 'wp-block-...' class names to imply an h-entry for default Wordpress (including .com) blog posts like https://librefm.wordpress.com/2024/10/13/whats-new-with-libre-fm-this-week-2024-10-13/

#
[pfefferle] [tantek] but in this actual case, not the nesting was the problem, but the missing attribute

#
[pfefferle] the h-entry was a direct child of the main h-entry

#
[pfefferle] [tantek] wp-block-* are the core block classes

#
[pfefferle] if a plugin introduces own blocks, the recommendation is to use a plugin "namespace" for that

#
[pfefferle] so the `wp-block-*` classes should be fairly stable

[will], sebbu2, [Joe_Crawford] and [jeremycherfas] joined the channel
#
[pfefferle] you are able to extend/modify blocks, but this is mostly about style not so much about renaming classes

gRegor, [qubyte], barnabywalters, to2ds and [KevinMarks] joined the channel