Conversation

Replying to and
Too many sites are using tons of JavaScript, so they would be entirely opaque to it. There's a lot of blog and forum software that requires JavaScript to display any results at all. Earlier versions of Discourse couldn't show anything without JavaScript and it had wide adoption.
2
One example: github.com/GrapheneOS/gra. Why doesn't Twitter use the normal description? It makes no sense to require repeating this on every page. I have no clue what the documented twitter:site / twitter:creator are meant to do. Can't wait to debug structured data for blog posts.
1
Look at that ugly GitHub link preview because they set <meta name="twitter:card" content="summary_large_image" /> and turn the user's avatar into a cropped rectangular banner. In my opinion, Twitter should be able to show link previews based on the standard title and description.
1
1
Should also use a standard site icon as the image if you don't override it for a page. I can't understand why I need to deal with all this nonsense. Nearly no sites / web developers do any of it properly. Open Graph metadata makes sense but it should be optional to override.
1
1
Also, HTML offers a standard content outline algorithm now, which you can use via an extension like chrome.google.com/webstore/detai, but too few sites support it. It's really nice on pages that are marked up sanely and could be a really nice thing for accessibility, but most sites suck.