I've been working on a jekyll plugin to make it easier to implement @standard.site: github.com/andrew/jekyll-standard-site

Wrote about messing around with @atproto.com and working on automatic syncing of content to @standard.site of my blog (and any blog) Bonus: it's open source and written in Elixir. Work in progress! jola.dev/posts/automatically-syncing-y…

I wrote out how I created my Hugo blog to then connect to @standard.site so that I could push my site to places like @standard-reader.app and other services that utilize ATProto. danarel.com/posts/blog-on-standard-site/

My @standard.site plugin for @craftcms.com is live! Find it on GitHub 👇 or on Craft's plugin store. Happy to hear feedback from both the #craftcms and the #atproto side 😀 github.com/studioespresso/craft-standard…

put up a post that includes a bunch of links I keep sending people over and over again also finally made my personal blog a @standard.site publication (thank u @awarm.space and @brookie.blog and @gu5.org for helping debug) :)

Had fun adding support for @standard.site to my blog. The richer preview card on #bsky looks neat. Another benefit is, since all the entries now live in the #ATmosphere, all kinds of #ATProto apps can index and display them. See pckt example: pckt.blog/read?search=rednafi rednafi.com/misc/standard-site/

atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935

atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935

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://…” \>

👀 @techdirt.com is now posting @standard.site compliant articles... Next up... backfilling our 80k+ article archives. But, for now, every new post should be using the @standard.site lexicon...

been working on a new Chrome extension to support @standard.site publications. install it and let me know what you think!

Sure seems like there’s nothing stopping @ghost.org from hopping on board the AT train now at very low dev cost. Would love for our existing Ghost blog to magically turn @standard.site compatible overnight.