=> Bluesky: link preview embeds sometime contain raw HTML

[snarfed]

Ugh. Example: https://bsky.app/profile/pcottle.threads.net.ap.brid.gy/post/3lczzpgrtsep2

From #microformats:

[snarfed] has anyone ever wanted to disable mf1 backcompat in an mf2 parser?
[snarfed] I'd like that option
[snarfed] example of bad results for parsing mf1 backcompat: https://pin13.net/mf2/?url=https://www.popsci.com/science/chain-reaction-the-hopeful-history-of-uranium-book-excerpt/
[tantek] those are some really weird false positives
[tantek] should we add "h-full" to our item blocklist?
[aaronpk] The php parser has that option https://github.com/microformats/php-mf2?tab=readme-ov-file#classic-microformats-markup
[snarfed] re h-full, sure, but I expect most/many mf2 consumers at least look for specific types they're interested in, so h-full wouldn't bother them too much...?
[snarfed] the real problem is the h-entry content there, at least for me
[snarfed] it may not technically be wrong, but it's not great
[tantek] yeah it's pretty bad
[tantek] I wonder if we could tweak it with some backcompat algo tweaks, e.g. if there's only a synthetic e-content (no author or name properties) then perhaps we should drop the entire synthetic h-entry?
[tantek] [snarfed] do you think such "reduce noise" efforts would be sufficient?
[tantek] or would this end up being a continuous patching exercise?
[snarfed] maybe!
[snarfed] honestly I don't know the ecosystem well enough to say
[gRegor] Some more discussion about those Tailwind classes in microformats/microformats2-parsing#59
[gRegor] [snarfed], is the problem the lack of the mf1 entry-title?
[gRegor] The entry-content looks mostly correct, though it includes the little holiday promo at the bottom which it probably shouldn't
[snarfed] yeah I don't have a crisp clear problem statement here, I just don't like it 😎
[snarfed] afaict this ugliness - even if it's technically correct - caused the URL and HTML in the link preview in https://bsky.app/profile/ScienceDesk.flipboard.social.ap.brid.gy/post/3lcgk6msncg42 instead of human-readable text, but I don't exactly understand how yet