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

it's easier than ever to turn your standard.site writing into your own website! your posts are atproto records you own. fetch & render them anywhere, in any framework, with your own styles. live demo, try any handle 👇 standard-publication-viewer.wisp.place?handle=erlend.sh

at:// links not opening in Firefox? Now they do ☄️ I made a tiny extension that redirects @atproto.com URIs to your preferred AppView — starting with @bsky.app @blackskyweb.xyz and @bluenotes.social 🩷 Works with posts, feeds, lists, starter packs and both @standard.site publication and documents 🔥

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

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

Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.

Seriously mild take: ATProto web clients should serve a <link rel="alternate"> containing an at:// URI I've just opened a PR to do this on Frontpage and atproto-browser. I'd for other clients to follow along with the convention! github.com/likeandscribe/frontpage/pull/…

@dholms.at and I pushed up IETF draft text for atproto repos and sync: ietf.org/archive/id/draft-holmgren-at-… ietf.org/archive/id/draft-holmgren-at-… these are versioned in github (per norm) over here: github.com/ietf-wg-atp/drafts

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…

atproto'd my website a bit further (beyond the @standard.site integration): 1) added a "Right now" box on the homage that pulls in all kinds of atproto activity like @bsky.app posts, @popfeed.social film ratings, @bookhive.buzz reads, @tangled.org repo's etc.

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/

Next stop, allow users to follow @standard.site publications directly from Glean. Atproto is great!