My blog is standard.site ready but I’m pausing full integration for now. I desperately wanted the fancy button but after its novelty wore off I’ve accepted the truth. The Bluesky button is bad UX. This has been widely complained about from day one.
The problem is obvious for Bluesky users. Clicking the fancy “View publication” button opens the homepage and not the actual article. This subverts the UI design pattern for ‘card’ components which is long established, evident by unhappy feedback.
I keep clicking the button myself despite knowing better.
I’ve seen Bluesky posts from Bluesky people suggesting this will change.
It was a design assumption for v1 that turned out to be … less than correct. We’re hard at work on v2.
It sure is taking a while! Ideally they’d benefit by pushing a quick fix for this alone. Maybe that’s not feasible for a project like Bluesky. It’s frustrating because it gives standard.site a bad smell that’ll be hard to shake off.
The easiest way to temporarily remove the button is to remove the <link> element.
<!-- <link rel="site.standard.document" href="..."> -->This is the document one for individual pages.
If I share my homepage I still get a button which uses the publication variation.
Unfortunately removing the metadata means my website is now not fully standard.site compliant. Although I am still publishing atproto records.
It’s possible Bluesky’s metadata extractor can be identified server-side and I could dynamically strip the element by user agent. I’m hosted on Bunny CDN so my only option would be to use a JavaScript worker. Bunny’s “edge scripting” add tens of milliseconds of latency to every page request which I’m not willing to entertain.
Let’s hope Bluesky fixes this soon because I reckon there’s something to
Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.