Update, 1 November 2026: hopper feeds ship, a new API, three rulings, and a reader test suite
Three working sessions in one day across the spec, Blygger Studio and the two sites. This is what changed, what it means if you run a node or build a client, and what is next.
Hopper feeds are live (Blygger Studio 0.50.0)
A public hopper, a curated collection on a blyg, can now be subscribed to on its own, without subscribing to the whole blyg it lives on. The request came from the World Machines bridge, which collects the posts its members put in a WM hopper. When it opened this morning, it had to work around the gap:
Hoppers don't have their own feeds yet, so the WM blyg follows your whole blyg in order to import posts. But it only collects the posts that are in the hopper you submitted.
from worldmachines.org ↗ · excerpt of v1
As of tonight they do, and a node on 0.50.0 can follow a member's hopper directly. Aneesh Sathe proposed the design (blygger-spec#18) and built it (blygger-studio#84). It was ruled in the afternoon as decision #86 and released tonight as 0.50.0.
- Turn it on under Settings → Network → hopper feeds. It is off by default.
- Each public hopper then has an RSS feed at
{mount}/h/{slug}/feed.xml, and the manifest gains ahopperslist naming them. - To subscribe, paste a hopper's page URL into Subscribe. The studio offers that hopper, with "whole blyg instead" beside it.
- Entries are summaries and links, newest-joined first. One that leaves the hopper leaves your reading at the next poll.
- Nothing about your own feed or item documents changes. A hopper feed carries no
blyg:markup, so it can never be mistaken for a second feed of your blyg, and no item document ever names a hopper. Hoppers stay a list, not tags.
The cross-node gate ran live: venkateshrao.com/blyg/ published a test hopper,
blyg.protocol-institute.org subscribed to it by pasting its page URL, removing a member
dropped the entry at the next poll, and the existing whole-blyg subscription between the
two nodes was untouched. On the strength of that, the rules moved from a ruled-but-unbuilt
appendix into the normative 0.4 text (eighth revision): §6.1 (hoppers), §12.1 step 7
(resolving a hopper URL), §12.2 (identity) and §13.5–§13.6 (the feed and the reader's
rules).
For other clients: to read hopper feeds, implement step 7. It needs no extra fetch: you
compare the URL you were given against the manifest's hoppers list. A reader that skips it
resolves a hopper URL to the whole blyg, exactly as before.
Also in 0.50.0, both from Aneesh: a partial quote now takes CommonMark's full blockquote,
so a line written directly under a > line is part of the passage, as it is when the quote
renders (#104). And an own-line
quote inside generated text that records its sources is now quoted at publish, as it
always was without sources (#105).
Migration 0038 runs before deploy.
A new private API (0.49.12)
Kyle Mathews' API cleanup landed earlier in the day: eleven pull requests tracked in blygger-studio#92.
- REST now lives at
{mount}/api. - Bodies are camelCase.
- Every item write names the revision it read, so two tools can't silently overwrite each other.
- Lists page by cursor, and media is addressed by its digest.
- REST and MCP share one set of operations.
This is private contract 5.0.0, now 5.1.0 with the hopper additions. On a node mounted at a
path, the old host-root /api still answers for two releases, with Deprecation and
successor Link headers. If you have a tool writing to a blyg, move it to {mount}/api
and send expectedRevision. This blyg's own publishing scripts needed exactly that change
tonight.
Three rulings (seventh revision of 0.4)
- #86: hopper feeds, above.
- #87: the fixed name holds at every identity. Wherever a blyg's identity origin is,
{origin}blyg.jsonMUST answer, as the manifest itself or by a same-identity redirect. A manifest may still be named elsewhere, but everyone who holds only an identity probes the fixed name, and two clients had disagreed about one live origin (blygger-spec#21, from chrisbodhi). - #88: origin succession. A blyg that moves says so twice: the old origin permanently
redirects its manifest, and the new one lists the old in an OPTIONAL
moved_from. Readers offer to follow only when both are there, and never adopt the new origin silently. This came from Florian Lohse's real move (blygger-studio#102). Until the studio builds it, one subscriber's copy was fixed by hand, and blygger.com now folds a moved blyg's old listing into its new one.
A reader conformance suite
Aneesh's reader suite
(blygger-spec#22) is merged in
conformance/reader/. It holds 100 fixtures, written from the spec text, that check what
any client's renderer bakes into content_html: quotes, labels, partial quotes, links,
absolute URLs and generation disclosure. Any renderer can run it through a small adapter.
Blygger Studio passed 72 of 100 against 0.49.12. Two of the four findings are fixed in 0.50.0,
and the other two (links[] and data-blyg-label) are queued. Nine places where the 0.4
text leaves a choice are now with Fable.
Also today
- Tangling is planned: top-down authoring where marked passages become fragments at publish. It comes with a reader-side Background lens, so bursts don't flood anyone. The heads-up post explains it, and what other clients can prepare.
- Contributors and ecosystem pages refreshed: Shannon, Ned Twigg, Florian Lohse, Rafael David and Ruthvik Peddawandla are credited, and blygd, blygcaster and blyg-watch are listed (contributors, ecosystem).
- Shannon's Base UI groundwork for the studio (blygger-studio#88) is in review.
Next
- The RFC-1 and RFC-2 comment periods close on 4 November.
- Building
moved_from. - The Background lens.
- Splitting the hopper-feeds setting, so a node can subscribe to hoppers without publishing feeds of its own.
Source: docs/posts/2026-11-01-update.md in blygger-spec, which is where revisions are made; each one is published here as a new version. To comment, respond to this item from your own blyg: a stub is a comment, a partial quote names the passage, and a fork of the pinned version is a counter-proposal.