{"blyg":"0.4","id":"7r19m93xew3gwrbr2rspp19t5n","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/7r19m93xew3gwrbr2rspp19t5n/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-02T07:00:29Z","updated":"2026-11-02T07:00:30Z","version":1,"content_md":"\n# Update, 1 November 2026: hopper feeds ship, a new API, three rulings, and a reader test suite\n\n*Three working sessions in one day across the spec, Blygger Studio and the two sites. This\nis what changed, what it means if you run a node or build a client, and what is next.*\n\n## Hopper feeds are live (Blygger Studio 0.50.0)\n\nA public hopper, a curated collection on a blyg, can now be **subscribed to on its own**,\nwithout subscribing to the whole blyg it lives on. The request came from the World Machines\nbridge, which collects the posts its members put in a WM hopper. When it opened this\nmorning, it had to work around the gap:\n\n\n![[4gth3c5hm6bvdgvt1mk3d9p1qa]]\n> 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.\n\n\nAs of tonight they do, and a node on 0.50.0 can follow a member's hopper directly. Aneesh Sathe proposed the design\n([blygger-spec#18](https://github.com/blygger/blygger-spec/pull/18)) and built it\n([blygger-studio#84](https://github.com/blygger/blygger-studio/pull/84)). It was ruled in\nthe afternoon as decision #86 and released tonight as **0.50.0**.\n\n- **Turn it on** under Settings → Network → hopper feeds. It is off by default.\n- Each public hopper then has an RSS feed at `{mount}/h/{slug}/feed.xml`, and the manifest\n  gains a `hoppers` list naming them.\n- **To subscribe**, paste a hopper's page URL into Subscribe. The studio offers that hopper,\n  with \"whole blyg instead\" beside it.\n- Entries are summaries and links, newest-joined first. One that leaves the hopper leaves\n  your reading at the next poll.\n- Nothing about your own feed or item documents changes. A hopper feed carries no `blyg:`\n  markup, so it can never be mistaken for a second feed of your blyg, and **no item\n  document ever names a hopper**. Hoppers stay a list, not tags.\n\nThe cross-node gate ran live: `venkateshrao.com/blyg/` published a test hopper,\n`blyg.protocol-institute.org` subscribed to it by pasting its page URL, removing a member\ndropped the entry at the next poll, and the existing whole-blyg subscription between the\ntwo nodes was untouched. On the strength of that, the rules moved from a ruled-but-unbuilt\nappendix into the normative 0.4 text (eighth revision): §6.1 (`hoppers`), §12.1 step 7\n(resolving a hopper URL), §12.2 (identity) and §13.5–§13.6 (the feed and the reader's\nrules).\n\n**For other clients:** to read hopper feeds, implement step 7. It needs no extra fetch: you\ncompare the URL you were given against the manifest's `hoppers` list. A reader that skips it\nresolves a hopper URL to the whole blyg, exactly as before.\n\nAlso in 0.50.0, both from Aneesh: a **partial quote** now takes CommonMark's full blockquote,\nso a line written directly under a `>` line is part of the passage, as it is when the quote\nrenders ([#104](https://github.com/blygger/blygger-studio/issues/104)). And an own-line\nquote inside **generated text that records its sources** is now quoted at publish, as it\nalways was without sources ([#105](https://github.com/blygger/blygger-studio/issues/105)).\nMigration 0038 runs before deploy.\n\n## A new private API (0.49.12)\n\nKyle Mathews' API cleanup landed earlier in the day: eleven pull requests tracked in\n[blygger-studio#92](https://github.com/blygger/blygger-studio/issues/92).\n\n- REST now lives at **`{mount}/api`**.\n- Bodies are camelCase.\n- Every item write names the revision it read, so two tools can't silently overwrite each\n  other.\n- Lists page by cursor, and media is addressed by its digest.\n- REST and MCP share one set of operations.\n\nThis is private contract 5.0.0, now 5.1.0 with the hopper additions. On a node mounted at a\npath, the old host-root `/api` still answers for two releases, with `Deprecation` and\nsuccessor `Link` headers. **If you have a tool writing to a blyg, move it to `{mount}/api`\nand send `expectedRevision`.** This blyg's own publishing scripts needed exactly that change\ntonight.\n\n## Three rulings (seventh revision of 0.4)\n\n- **#86: hopper feeds**, above.\n- **#87: the fixed name holds at every identity.** Wherever a blyg's identity origin is,\n  `{origin}blyg.json` MUST answer, as the manifest itself or by a same-identity redirect. A\n  manifest may still be *named* elsewhere, but everyone who holds only an identity probes the\n  fixed name, and two clients had disagreed about one live origin\n  ([blygger-spec#21](https://github.com/blygger/blygger-spec/issues/21), from chrisbodhi).\n- **#88: origin succession.** A blyg that moves says so twice: the old origin permanently\n  redirects its manifest, and the new one lists the old in an OPTIONAL `moved_from`. Readers\n  offer to follow only when both are there, and never adopt the new origin silently. This\n  came from Florian Lohse's real move\n  ([blygger-studio#102](https://github.com/blygger/blygger-studio/issues/102)). Until the\n  studio builds it, one subscriber's copy was fixed by hand, and blygger.com now folds a\n  moved blyg's old listing into its new one.\n\n## A reader conformance suite\n\nAneesh's **reader suite**\n([blygger-spec#22](https://github.com/blygger/blygger-spec/pull/22)) is merged in\n`conformance/reader/`. It holds 100 fixtures, written from the spec text, that check what\nany client's renderer bakes into `content_html`: quotes, labels, partial quotes, links,\nabsolute URLs and generation disclosure. Any renderer can run it through a small adapter.\nBlygger Studio passed 72 of 100 against 0.49.12. Two of the four findings are fixed in 0.50.0,\nand the other two (`links[]` and `data-blyg-label`) are queued. Nine places where the 0.4\ntext leaves a choice are now with Fable.\n\n## Also today\n\n- **Tangling is planned**: top-down authoring where marked passages become fragments at\n  publish. It comes with a reader-side Background lens, so bursts don't flood anyone. The\n  [heads-up post](https://blyg.blygger.org/t/2c494ntcyfgt5f2agqmb7vmsye/) explains it, and\n  what other clients can prepare.\n- **Contributors and ecosystem pages refreshed**: Shannon, Ned Twigg, Florian Lohse, Rafael\n  David and Ruthvik Peddawandla are credited, and blygd, blygcaster and blyg-watch are\n  listed ([contributors](https://blygger.org/contributors/),\n  [ecosystem](https://blygger.org/ecosystem/)).\n- Shannon's Base UI groundwork for the studio\n  ([blygger-studio#88](https://github.com/blygger/blygger-studio/pull/88)) is in review.\n\n## Next\n\n- The RFC-1 and RFC-2 comment periods close on 4 November.\n- Building `moved_from`.\n- The Background lens.\n- Splitting the hopper-feeds setting, so a node can subscribe to hoppers without publishing\n  feeds of its own.\n\n\n\n*Source: [`docs/posts/2026-11-01-update.md`](https://github.com/blygger/blygger-spec/blob/main/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.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Update, 1 November 2026: hopper feeds ship, a new API, three rulings, and a reader test suite</h1>\n<p><em>Three working sessions in one day across the spec, Blygger Studio and the two sites. This\nis what changed, what it means if you run a node or build a client, and what is next.</em></p>\n<h2>Hopper feeds are live (Blygger Studio 0.50.0)</h2>\n<p>A public hopper, a curated collection on a blyg, can now be <strong>subscribed to on its own</strong>,\nwithout subscribing to the whole blyg it lives on. The request came from the World Machines\nbridge, which collects the posts its members put in a WM hopper. When it opened this\nmorning, it had to work around the gap:</p>\n</div>\n\n<blockquote class=\"blyg-transclusion blyg-partial\" data-blyg-id=\"4gth3c5hm6bvdgvt1mk3d9p1qa\" data-blyg-version=\"1\" data-blyg-origin=\"https://blyg.worldmachines.org/\">\n<p>Hoppers don&#39;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.</p>\n</blockquote>\n<div class=\"blyg-tk-gen\"><p>As of tonight they do, and a node on 0.50.0 can follow a member's hopper directly. Aneesh Sathe proposed the design\n(<a href=\"https://github.com/blygger/blygger-spec/pull/18\">blygger-spec#18</a>) and built it\n(<a href=\"https://github.com/blygger/blygger-studio/pull/84\">blygger-studio#84</a>). It was ruled in\nthe afternoon as decision #86 and released tonight as <strong>0.50.0</strong>.</p>\n<ul>\n<li><strong>Turn it on</strong> under Settings → Network → hopper feeds. It is off by default.</li>\n<li>Each public hopper then has an RSS feed at <code>{mount}/h/{slug}/feed.xml</code>, and the manifest\ngains a <code>hoppers</code> list naming them.</li>\n<li><strong>To subscribe</strong>, paste a hopper's page URL into Subscribe. The studio offers that hopper,\nwith &quot;whole blyg instead&quot; beside it.</li>\n<li>Entries are summaries and links, newest-joined first. One that leaves the hopper leaves\nyour reading at the next poll.</li>\n<li>Nothing about your own feed or item documents changes. A hopper feed carries no <code>blyg:</code>\nmarkup, so it can never be mistaken for a second feed of your blyg, and <strong>no item\ndocument ever names a hopper</strong>. Hoppers stay a list, not tags.</li>\n</ul>\n<p>The cross-node gate ran live: <code>venkateshrao.com/blyg/</code> published a test hopper,\n<code>blyg.protocol-institute.org</code> subscribed to it by pasting its page URL, removing a member\ndropped the entry at the next poll, and the existing whole-blyg subscription between the\ntwo nodes was untouched. On the strength of that, the rules moved from a ruled-but-unbuilt\nappendix into the normative 0.4 text (eighth revision): §6.1 (<code>hoppers</code>), §12.1 step 7\n(resolving a hopper URL), §12.2 (identity) and §13.5–§13.6 (the feed and the reader's\nrules).</p>\n<p><strong>For other clients:</strong> to read hopper feeds, implement step 7. It needs no extra fetch: you\ncompare the URL you were given against the manifest's <code>hoppers</code> list. A reader that skips it\nresolves a hopper URL to the whole blyg, exactly as before.</p>\n<p>Also in 0.50.0, both from Aneesh: a <strong>partial quote</strong> now takes CommonMark's full blockquote,\nso a line written directly under a <code>&gt;</code> line is part of the passage, as it is when the quote\nrenders (<a href=\"https://github.com/blygger/blygger-studio/issues/104\">#104</a>). And an own-line\nquote inside <strong>generated text that records its sources</strong> is now quoted at publish, as it\nalways was without sources (<a href=\"https://github.com/blygger/blygger-studio/issues/105\">#105</a>).\nMigration 0038 runs before deploy.</p>\n<h2>A new private API (0.49.12)</h2>\n<p>Kyle Mathews' API cleanup landed earlier in the day: eleven pull requests tracked in\n<a href=\"https://github.com/blygger/blygger-studio/issues/92\">blygger-studio#92</a>.</p>\n<ul>\n<li>REST now lives at <strong><code>{mount}/api</code></strong>.</li>\n<li>Bodies are camelCase.</li>\n<li>Every item write names the revision it read, so two tools can't silently overwrite each\nother.</li>\n<li>Lists page by cursor, and media is addressed by its digest.</li>\n<li>REST and MCP share one set of operations.</li>\n</ul>\n<p>This is private contract 5.0.0, now 5.1.0 with the hopper additions. On a node mounted at a\npath, the old host-root <code>/api</code> still answers for two releases, with <code>Deprecation</code> and\nsuccessor <code>Link</code> headers. <strong>If you have a tool writing to a blyg, move it to <code>{mount}/api</code>\nand send <code>expectedRevision</code>.</strong> This blyg's own publishing scripts needed exactly that change\ntonight.</p>\n<h2>Three rulings (seventh revision of 0.4)</h2>\n<ul>\n<li><strong>#86: hopper feeds</strong>, above.</li>\n<li><strong>#87: the fixed name holds at every identity.</strong> Wherever a blyg's identity origin is,\n<code>{origin}blyg.json</code> MUST answer, as the manifest itself or by a same-identity redirect. A\nmanifest may still be <em>named</em> elsewhere, but everyone who holds only an identity probes the\nfixed name, and two clients had disagreed about one live origin\n(<a href=\"https://github.com/blygger/blygger-spec/issues/21\">blygger-spec#21</a>, from chrisbodhi).</li>\n<li><strong>#88: origin succession.</strong> A blyg that moves says so twice: the old origin permanently\nredirects its manifest, and the new one lists the old in an OPTIONAL <code>moved_from</code>. Readers\noffer to follow only when both are there, and never adopt the new origin silently. This\ncame from Florian Lohse's real move\n(<a href=\"https://github.com/blygger/blygger-studio/issues/102\">blygger-studio#102</a>). Until the\nstudio builds it, one subscriber's copy was fixed by hand, and <a href=\"http://blygger.com\">blygger.com</a> now folds a\nmoved blyg's old listing into its new one.</li>\n</ul>\n<h2>A reader conformance suite</h2>\n<p>Aneesh's <strong>reader suite</strong>\n(<a href=\"https://github.com/blygger/blygger-spec/pull/22\">blygger-spec#22</a>) is merged in\n<code>conformance/reader/</code>. It holds 100 fixtures, written from the spec text, that check what\nany client's renderer bakes into <code>content_html</code>: quotes, labels, partial quotes, links,\nabsolute URLs and generation disclosure. Any renderer can run it through a small adapter.\nBlygger Studio passed 72 of 100 against 0.49.12. Two of the four findings are fixed in 0.50.0,\nand the other two (<code>links[]</code> and <code>data-blyg-label</code>) are queued. Nine places where the 0.4\ntext leaves a choice are now with Fable.</p>\n<h2>Also today</h2>\n<ul>\n<li><strong>Tangling is planned</strong>: top-down authoring where marked passages become fragments at\npublish. It comes with a reader-side Background lens, so bursts don't flood anyone. The\n<a href=\"https://blyg.blygger.org/t/2c494ntcyfgt5f2agqmb7vmsye/\">heads-up post</a> explains it, and\nwhat other clients can prepare.</li>\n<li><strong>Contributors and ecosystem pages refreshed</strong>: Shannon, Ned Twigg, Florian Lohse, Rafael\nDavid and Ruthvik Peddawandla are credited, and blygd, blygcaster and blyg-watch are\nlisted (<a href=\"https://blygger.org/contributors/\">contributors</a>,\n<a href=\"https://blygger.org/ecosystem/\">ecosystem</a>).</li>\n<li>Shannon's Base UI groundwork for the studio\n(<a href=\"https://github.com/blygger/blygger-studio/pull/88\">blygger-studio#88</a>) is in review.</li>\n</ul>\n<h2>Next</h2>\n<ul>\n<li>The RFC-1 and RFC-2 comment periods close on 4 November.</li>\n<li>Building <code>moved_from</code>.</li>\n<li>The Background lens.</li>\n<li>Splitting the hopper-feeds setting, so a node can subscribe to hoppers without publishing\nfeeds of its own.</li>\n</ul>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>Source: <a href=\"https://github.com/blygger/blygger-spec/blob/main/docs/posts/2026-11-01-update.md\"><code>docs/posts/2026-11-01-update.md</code></a> 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.</em></p>\n</div>\n","content_hash":"sha256:9a38564a6cd64b0fca4abfd98ebf99484cd8dfd56b2bc03d0ceb5c1451c210d3","media":[],"transclusions":[{"id":"4gth3c5hm6bvdgvt1mk3d9p1qa","version":1,"origin":"https://blyg.worldmachines.org/","selector":{"exact":"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.","prefix":"blyg reads every listed hopper.\n","suffix":"\nCollected posts are filed in th"},"cited":{"source":"worldmachines.org","excerpt":"World Machines blyg now active and accepting hoppers: https://blyg.worldmachines…","url":"https://blyg.worldmachines.org/t/4gth3c5hm6bvdgvt1mk3d9p1qa/","retrieved":"2026-11-02T07:00:30Z"}}],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-02T07:00:30Z","note":"Update for 1 November 2026: hopper feeds ship in 0.50.0, the 0.49 API, rulings #86–#88, the reader suite."}]}