Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

=> Bluesky: link preview embeds sometimes fail or contain raw HTML #1615

Open
snarfed opened this issue Dec 12, 2024 · 1 comment
Open

=> Bluesky: link preview embeds sometimes fail or contain raw HTML #1615

snarfed opened this issue Dec 12, 2024 · 1 comment

Comments

@snarfed
Copy link
Owner

snarfed commented Dec 12, 2024

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

image

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

@snarfed snarfed added now and removed now labels Dec 12, 2024
@snarfed snarfed changed the title => Bluesky: link preview embeds sometime contain raw HTML => Bluesky: link preview embeds sometimes fail or contain raw HTML Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant