The day in Blygger, 17 October 2026: protocol 0.4, labels, and a new front page

Protocol 0.4 opened and was published with its first snapshot, then took two revisions the same evening. Nine decisions were recorded, #70 through #78: the [[id | text]] label, received conventions over taste, the 0.4 opening, the pace-layered RFC with pinned_at, cid on pins, image sizing, the conformance clarifications with member tables measured against all 22 live blygs, ignyr as a derived reader-side queue, and inline fragment authoring. Three pending Opus rulings were confirmed. Five GitHub threads were answered and one closed. The Fable queue went from seventeen items to one.

If you run a blyg

• Blygger Studio 0.47.0 is the first client to write the new label: [[id | text]] on a link sets its text, ![[id | a note]] on a quote keeps a thread's source readable and never reaches readers. The picker and copy [[id]] write the long form for you. Generated text no longer publishes stray brackets.
• Blygger Studio 0.46.3 carries Kyle Mathews' fix for OAuth clients that leave out resource, which may be what kept the MCP server out of Cloudflare's MCP portals (studio#54), and hover text on the editor toolbar (Ned Twigg, studio#48).
• blygger.com now hands subscribers each blyg's own feed, as its manifest names it, so a blyg on WordPress via Soapbox for Blygger is listed with a feed that works.
• blygger.org has a new front page in two tabs, For Publishers and For Developers, a glossary, and a page on the thicket, the network of blygs formerly called the blygosphere, with the idea for an explorer of it, which will live on blygger.com.

If you write a client

• 0.4's new constructs: a generator may draw on another blyg's item, disclosed as a source that notifies its origin (§5.7, §15.4); a manifest may say where its feed, items and pins live (§4, §6.1); and the optional label after an id (§10.1). A valid 0.3 document is a valid 0.4 document.
• Ruled shapes you could build now (§16): pinned_at on pinned changelog entries, cid naming a pinned document's exact bytes (spec#13), and Pandoc-style {width=…} on images (studio#37).
• Clarified: member tables for item documents and manifests, eight conformance findings from Aneesh Sathe's toolkit, a same-hash republish as maintenance rather than news, and multi-item publishes (one event per item, thread last), which readers may fold into one publication (studio#20).
• Coming: RFC-3, the pace-layered order as a recommendation for every client. RFC-1 (mentions) and RFC-2 (comments sections) stay open for comment on this blyg until 4 November.

Threads

spec#2 closed: Robert Peake's Soapbox switches to "0.4". spec#16, Ned Twigg's request for comments inside ids, ruled and shipped. Surya Kasturi's questions on Webmention flooding, DNS firewalls and feed scoring answered (studio#72, #49, #57); Aneesh's studio#11 closed with everything on its list shipped, and his extension registry (studio#59) is next for a ruling. And a question for Kyle on whether a CI check should depend on outside registries (studio#73).

Everything above is on the roadmap, and comments are welcome as stubs of this post.