{"blyg":"0.4","id":"60czrxc7x27zpzm42fdz41eesn","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/60czrxc7x27zpzm42fdz41eesn/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-04T23:20:16Z","updated":"2026-11-04T23:20:17Z","version":1,"content_md":"\n# Two studio releases, and planning for private posts and enterprise use\n\n*Blygger Studio 0.52.0 and 0.53.0 shipped on 2026-11-04, and both are live on the\nfour reference nodes. The day also started two planning threads: private posts, and\nBlygger inside organisations. This post summarises both. The full record is the\n[program devlog](https://github.com/blygger/blygger-spec/blob/main/DEVLOG.md).*\n\n## Faster reading, and reads that cost less\n\n**0.52.0** is mostly about the reader using less of the database.\n\n- **Batched reads** (Kyle Mathews, studio#114). Independent reads on a studio page now\n  travel together in one request. On the server, the database statements in each\n  batch share calls. Mentions opens with 10 posts and 10 mentions each. In review,\n  the browser half turned out to wait on a timer, which browsers throttle in background\n  tabs; Kyle switched it to dispatch without timers before it merged.\n- **Two table scans removed** (studio#113, reported by patwater, fixed in #115). On\n  Cloudflare's free plan, database rows read count against a daily limit, and one\n  owner's reader was using it up. The main cause, the inbox ordering, was fixed in\n  0.49.12, so nodes older than that should upgrade. The report also surfaced two\n  lookups that still read whole tables: finding an item you follow by its id, and\n  listing which collections each reading entry is in. Both now use an index.\n- **Collections without your own collection feeds** (Aneesh Sathe, studio#112). You\n  can subscribe to another blyg's public collection whether or not your node publishes\n  collection feeds of its own.\n\n## Search, and studios you can tell apart\n\n**0.53.0** adds things you can see.\n\n- **Search on the reading and compose pages** (studio#120). It is the same search the\n  `[[` picker runs. Type in the box at the top, and the results replace the list. The\n  search goes in the address, so the back button returns to your results. On the\n  reading page, it searches the source you have selected, with a button to widen it.\n  On the compose page, it searches your own blyg by default, drafts included.\n- **The login page wears your blyg's theme** (studio#119). It used to be the studio's\n  default blue.\n- **Each studio's browser tab says which blyg it is** (studio#121). The title names the\n  blyg, and the ❝ icon takes the theme's accent colour. If you run several blygs, you\n  can now tell the tabs apart without clicking in.\n- **Read batches are more robust** (Kyle Mathews, studio#116). A malformed address in\n  one read no longer fails the reads around it.\n\nBoth releases have announcements on this blyg with their full notes. The release posts\nfor 0.49.1, 0.49.12, 0.50.0 and 0.51.0, which had been missed, went up the same day.\n\n## Planning: private posts\n\nA **private** level for posts is being worked out. It is for finished work you\nhaven't decided whether to publish. The current shape, from an exploration in\nblygger-spec (`plans/private-items-proposal.md`):\n\n- **Visibility goes user / group / public**, like Unix permissions, and is separate\n  from draft. A private post can have versions and pending changes like a public one.\n  Only public posts are ever served.\n- **A private post can be quoted and linked from your own drafts and private posts.**\n  Publishing anything that refers to it is blocked until you remove the reference or\n  make the private post public first.\n- **Group** (a named set of readers) is the protocol's deferred privileged-access level.\n  It waits for a design round of its own.\n- One question goes to the protocol's design review: when a post that reached its third\n  private version goes public, does it start at version 1 on the wire?\n\nNothing is built yet.\n\n## Planning: Blygger inside organisations\n\nA draft RFC asks whether anything fundamental stops Blygger being used inside an\norganisation: on an internal network, behind single sign-on, under retention rules.\nThe short answer is **no, not at the protocol level.**\n\n- Nothing in the protocol assumes the public internet. A blyg on an internal network,\n  or behind a sign-on gate, is a blyg whose audience is everyone who can reach it.\n- Different readers seeing different posts *within one blyg* is the deferred\n  privileged-access level again. One blyg per audience works today.\n- The real risks are a quote of internal work copying it out (a quote bakes the text)\n  and retention law running against \"published stays published\".\n\nThe RFC is written for anyone building an enterprise product on Blygger, which is\nexpected to be a client of its own. After a design review it will be published here\nfor comment, then become a technical note.\n\n## Where the code is\n\n- [Blygger Studio releases](https://github.com/blygger/blygger-studio/releases)\n- [The 0.4 spec](https://blygger.org/spec/0.4/), now at its ninth revision\n- [Modding the Studio](https://github.com/blygger/blygger-studio/blob/main/docs/mods.md),\n  published this week, linked from the [ecosystem page](https://blygger.org/ecosystem/)\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Two studio releases, and planning for private posts and enterprise use</h1>\n<p><em>Blygger Studio 0.52.0 and 0.53.0 shipped on 2026-11-04, and both are live on the\nfour reference nodes. The day also started two planning threads: private posts, and\nBlygger inside organisations. This post summarises both. The full record is the\n<a href=\"https://github.com/blygger/blygger-spec/blob/main/DEVLOG.md\">program devlog</a>.</em></p>\n<h2>Faster reading, and reads that cost less</h2>\n<p><strong>0.52.0</strong> is mostly about the reader using less of the database.</p>\n<ul>\n<li><strong>Batched reads</strong> (Kyle Mathews, studio#114). Independent reads on a studio page now\ntravel together in one request. On the server, the database statements in each\nbatch share calls. Mentions opens with 10 posts and 10 mentions each. In review,\nthe browser half turned out to wait on a timer, which browsers throttle in background\ntabs; Kyle switched it to dispatch without timers before it merged.</li>\n<li><strong>Two table scans removed</strong> (studio#113, reported by patwater, fixed in #115). On\nCloudflare's free plan, database rows read count against a daily limit, and one\nowner's reader was using it up. The main cause, the inbox ordering, was fixed in\n0.49.12, so nodes older than that should upgrade. The report also surfaced two\nlookups that still read whole tables: finding an item you follow by its id, and\nlisting which collections each reading entry is in. Both now use an index.</li>\n<li><strong>Collections without your own collection feeds</strong> (Aneesh Sathe, studio#112). You\ncan subscribe to another blyg's public collection whether or not your node publishes\ncollection feeds of its own.</li>\n</ul>\n<h2>Search, and studios you can tell apart</h2>\n<p><strong>0.53.0</strong> adds things you can see.</p>\n<ul>\n<li><strong>Search on the reading and compose pages</strong> (studio#120). It is the same search the\n<code>[[</code> picker runs. Type in the box at the top, and the results replace the list. The\nsearch goes in the address, so the back button returns to your results. On the\nreading page, it searches the source you have selected, with a button to widen it.\nOn the compose page, it searches your own blyg by default, drafts included.</li>\n<li><strong>The login page wears your blyg's theme</strong> (studio#119). It used to be the studio's\ndefault blue.</li>\n<li><strong>Each studio's browser tab says which blyg it is</strong> (studio#121). The title names the\nblyg, and the ❝ icon takes the theme's accent colour. If you run several blygs, you\ncan now tell the tabs apart without clicking in.</li>\n<li><strong>Read batches are more robust</strong> (Kyle Mathews, studio#116). A malformed address in\none read no longer fails the reads around it.</li>\n</ul>\n<p>Both releases have announcements on this blyg with their full notes. The release posts\nfor 0.49.1, 0.49.12, 0.50.0 and 0.51.0, which had been missed, went up the same day.</p>\n<h2>Planning: private posts</h2>\n<p>A <strong>private</strong> level for posts is being worked out. It is for finished work you\nhaven't decided whether to publish. The current shape, from an exploration in\nblygger-spec (<code>plans/private-items-proposal.md</code>):</p>\n<ul>\n<li><strong>Visibility goes user / group / public</strong>, like Unix permissions, and is separate\nfrom draft. A private post can have versions and pending changes like a public one.\nOnly public posts are ever served.</li>\n<li><strong>A private post can be quoted and linked from your own drafts and private posts.</strong>\nPublishing anything that refers to it is blocked until you remove the reference or\nmake the private post public first.</li>\n<li><strong>Group</strong> (a named set of readers) is the protocol's deferred privileged-access level.\nIt waits for a design round of its own.</li>\n<li>One question goes to the protocol's design review: when a post that reached its third\nprivate version goes public, does it start at version 1 on the wire?</li>\n</ul>\n<p>Nothing is built yet.</p>\n<h2>Planning: Blygger inside organisations</h2>\n<p>A draft RFC asks whether anything fundamental stops Blygger being used inside an\norganisation: on an internal network, behind single sign-on, under retention rules.\nThe short answer is <strong>no, not at the protocol level.</strong></p>\n<ul>\n<li>Nothing in the protocol assumes the public internet. A blyg on an internal network,\nor behind a sign-on gate, is a blyg whose audience is everyone who can reach it.</li>\n<li>Different readers seeing different posts <em>within one blyg</em> is the deferred\nprivileged-access level again. One blyg per audience works today.</li>\n<li>The real risks are a quote of internal work copying it out (a quote bakes the text)\nand retention law running against &quot;published stays published&quot;.</li>\n</ul>\n<p>The RFC is written for anyone building an enterprise product on Blygger, which is\nexpected to be a client of its own. After a design review it will be published here\nfor comment, then become a technical note.</p>\n<h2>Where the code is</h2>\n<ul>\n<li><a href=\"https://github.com/blygger/blygger-studio/releases\">Blygger Studio releases</a></li>\n<li><a href=\"https://blygger.org/spec/0.4/\">The 0.4 spec</a>, now at its ninth revision</li>\n<li><a href=\"https://github.com/blygger/blygger-studio/blob/main/docs/mods.md\">Modding the Studio</a>,\npublished this week, linked from the <a href=\"https://blygger.org/ecosystem/\">ecosystem page</a></li>\n</ul>\n</div>\n","content_hash":"sha256:c9b2e590bd73791a852dad5f9719362c6663f3102f42331da0328acd9d887452","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-04T23:20:17Z","note":"Session 59 summary."}]}