{"blyg":"0.4","id":"0jwr7x38zkf7gazr0ckkmp8dn4","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/0jwr7x38zkf7gazr0ckkmp8dn4/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-10-10T01:58:04Z","updated":"2026-10-10T01:58:04Z","version":1,"content_md":"\n# Blygger Studio 0.39.0\n\n*Released 2026-10-09, the reference client. [v0.39.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.39.0).*\n\n**Migrations: `0026_read_state.sql`** (a `read_state` table and five triggers).\nApply it before deploying: `wrangler d1 migrations apply <database> --remote`.\n\n- **Read state for imported items** (Aneesh Sathe, #44 and #45). Reading\n  entries show an unread dot. Opening an entry marks it read, and a select mode\n  marks several read or unread at once, or the whole feed read. Read state is\n  stored per imported item with the version you read, so a new version of an\n  item shows as unread again. Marking unread leaves a tombstone, so a stale\n  \"read\" from a client that was offline cannot undo it. It stays in the studio:\n  nothing about it reaches the feed, the item documents or other blygs.\n- **API:** `PUT` and `DELETE /api/reading/{sub}/{remoteId}/read`, the batch\n  routes `POST /api/reading/read` and `POST /api/reading/unread` (up to the\n  batch limit in one write), and `readVersion` on `GET /api/reading`. A change\n  advances the `reading` revision in `GET /api/changes`. Read state is deleted\n  along with its imported item or subscription.\n- **A new scope, `reading:state`**, for marking read and unread. A reader app\n  that only syncs read state does not need `owner:manage`, which can also\n  delete subscriptions, and `owner:manage` does not include read state. Existing\n  grants are unchanged; a client that wants read state asks for the new scope.\n\n\n\n*This announcement is drafted from the release's section of [`CHANGELOG.md`](https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md), which is where it is maintained. To comment, respond to this item from your own blyg.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Blygger Studio 0.39.0</h1>\n<p><em>Released 2026-10-09, the reference client. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.39.0\">v0.39.0 on GitHub</a>.</em></p>\n<p><strong>Migrations: <code>0026_read_state.sql</code></strong> (a <code>read_state</code> table and five triggers).\nApply it before deploying: <code>wrangler d1 migrations apply &lt;database&gt; --remote</code>.</p>\n<ul>\n<li><strong>Read state for imported items</strong> (Aneesh Sathe, #44 and #45). Reading\nentries show an unread dot. Opening an entry marks it read, and a select mode\nmarks several read or unread at once, or the whole feed read. Read state is\nstored per imported item with the version you read, so a new version of an\nitem shows as unread again. Marking unread leaves a tombstone, so a stale\n&quot;read&quot; from a client that was offline cannot undo it. It stays in the studio:\nnothing about it reaches the feed, the item documents or other blygs.</li>\n<li><strong>API:</strong> <code>PUT</code> and <code>DELETE /api/reading/{sub}/{remoteId}/read</code>, the batch\nroutes <code>POST /api/reading/read</code> and <code>POST /api/reading/unread</code> (up to the\nbatch limit in one write), and <code>readVersion</code> on <code>GET /api/reading</code>. A change\nadvances the <code>reading</code> revision in <code>GET /api/changes</code>. Read state is deleted\nalong with its imported item or subscription.</li>\n<li><strong>A new scope, <code>reading:state</code></strong>, for marking read and unread. A reader app\nthat only syncs read state does not need <code>owner:manage</code>, which can also\ndelete subscriptions, and <code>owner:manage</code> does not include read state. Existing\ngrants are unchanged; a client that wants read state asks for the new scope.</li>\n</ul>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>This announcement is drafted from the release's section of <a href=\"https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md\"><code>CHANGELOG.md</code></a>, which is where it is maintained. To comment, respond to this item from your own blyg.</em></p>\n</div>\n","content_hash":"sha256:be4bcf0d1932924da7b4e003b4b522ef465da441f5a2efe5ce7b64a65759463c","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-10-10T01:58:04Z","note":"Studio 0.39.0 released."}]}