I found a really great article around web standards "Every feature begins life as a non-standard proposal, often shipped. This is not a bug" that I shared with @blaine.bsky.social last September. Thread in the forum discourse.atprotocol.community/t/web-standards-and-the-fall-…
Web Standards and the Fall of the House of Iamus (Alex Russell)
discourse.atprotocol.community
Blaine
I need to write more about this, but one of the core benefits of atproto is that it (dramatically) lowers the cost of coordination, both in divergence and convergence.
Jun 8, 2026 at 8:54 PM
On forking the Web
This document contains a set of informal notes on how to build an alternative specification to the Web, in such a way that hopefully prevents many of its drawbacks while still preserves many of the good points. This document is not an specification, and is therefore subject to change over time.
WebAssembly Core Specification
Please check the errata for any errors or issues reported since publication.
Your writing, now native to Bluesky | Offprint
Building an open standard only works if others build on it too. When we started Standard.site (@standard.site) alongside...
#protocolsforpublishers #atproto #mcp #webapplets | Chad Kohalyk
Web publishing is facing its next challenge: a new iteration of centralizing platforms. BUT there is also a new wave of open protocols and standards that can help us gain our independence. Next month in NYC we are gathering a group of frontier technologists and popular web publishers to discuss how we can sail into this next platform shift as captains. #ProtocolsForPublishers Learn more and sign up here: https://pfp.unternet.co We will be hosting talks on #atproto #mcp #webapplets and web payments, and give publishers the opportunity to interact directly with developers working on these frontier technologies. Thank you to Unternet, Graze Social, Free our Feeds, and betaworks for their support.
The Browser Company explains why it stopped developing Arc
Arc browser is now in a holding pattern.
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
On March 29th, we held an in-person meeting to check in with the community and discuss potential updates to the standard.site spec. A huge thank you to @cozylittle.house for putting together a detailed summary of everything we discussed. leaflet.pub/p/did:plc:kydzcmnywraao2srchq…
Standard Site Working Group Meeting Notes 3/29/26
leaflet.pubI 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://…” \>
rich harris
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
It's release week at the house, and here's our next announcement: Mise en Mode, the emerging web standard! AT Protocol is a federated model for building social media apps like Bluesky. We want folks in the Atmosphere to adopt for supporting a visitor's own look over their own. standard.mode.place
standard.mode.place: carry your look from app to app
standard.mode.placeAtproto has never required HTTP megastructure. April 2023:
dietrich
@why.bsky.team how locked to the http+dns+ssl nexus of publisher-centric control is atproto? i see https noted briefly in xrpc docs. how local+offline and transport agnostic can we get here? bluetooth / mdns / laser / pigeon transports possible?
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
at:// link in svelte:head gives error in pre-render mode · Issue #15935 · sveltejs/kit
github.comThis generated some discussion so I want to expand on it a bit The context is that standard.site doesn't currently have any lexicons for the actual content. The idea is that the document content is covered by leaflet, offprint, pckt, or other lexicons. But...
Paul Frazee
You shouldn’t use lexicons that don’t actually exist
It's the summer of standard.site and overwhelmingly, we've heard folks find the process complicated so Declan Chidlow is here to break the process down into something rather straightforward for you. piccalil.li/blog/publishing-on-the-atmosp…
Publishing on the Atmosphere with Standard.site
piccalil.li
