has anyone done an explainer on why standard.site is cool? I can usually see the promise in new developments here and I'm sure I'm missing something but I'm just not getting it

We wrote a @standard.site explainer — what it is & why it's useful 📝✨ ~shared standards for longform publishing? ~a way to see what friends read & write? ~the atmosphere's hottest collab? yes yes & yes! Seeing lots of q's after Bluesky's new standard.site link card integration. Here's a TL;DR!

The confusion about standard.site is that there are two distinct and different users. Those that use it as a database schema and those that use it as a new syndication format (like a Wordpress blog with a plugin). But HTML and RSS are views, whereas JSON doubles as both a storage schema and a view

I think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>

got me thinking too, we should create a standard way for standard site hosts to expose embedable content. Maybe an html subset, maybe just an iframe, maybe something else?

A standard similar to standard.site but for storefronts could be cool, standard.shop?

Added support for Standard.site to cross-posted Bluesky posts. This is a new convention for long-form blogging using the AT Protocol. Initially, you can think of it as extra metadata for your blog posts on Bluesky, with more interoperability between platforms possible later.