{"blyg":"0.4","id":"3psqv9wj3f52yxjanxn06a4tq0","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/3psqv9wj3f52yxjanxn06a4tq0/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-15T05:15:58Z","updated":"2026-11-15T05:15:58Z","version":1,"content_md":"\n# Blygger Studio 0.60.0: Download a backup, discover blygs\n\n*Released 2026-11-14, the reference client. [v0.60.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.60.0).*\n\n**Download backup** (ROADMAP row 15). More → *download backup* streams the whole blyg as\none `.tar` from `{studio}/backup`: every database table as JSON lines under `tables/`,\npaged so no table is held in memory, every uploaded file under `media/` by its storage\nkey, a `README.txt`, and `backup.json` last, naming the client, the latest applied\nmigration and the counts, with `complete: true`. A backup without `backup.json` did not\nfinish. Plain tar, since media is already compressed. The owner's browser session only,\nnever a delegated token. Left out: the OAuth and security tables (grants, tokens, signing\nkeys, rate-limit budgets), wrangler's migration ledger and the feed cache. Restoring one\ninto a fresh node is row 53 and not built.\n\nThe button is marked beta: it runs inside one Worker request, which caps storage reads,\nso on a blyg with very many files it can stop partway (and then has no `backup.json`).\nFor those, **`npm run backup -- --base https://your.blyg/ [--env NAME]`** makes the same\narchive from a deployment checkout through `wrangler`, one request per table page and per\nfile with retries, so the cap does not apply; a large blyg is only slower. It uses your\n`wrangler login` session and the deployment's wrangler config. `npm run export` is still\nthe public site only, for moving to a static host, not a backup.\n\nTables are copied by allow-list. The auth library makes its own tables at runtime\n(`session`, `jwks`, `oauthAccessToken`, `user` and kin), outside `migrations/`; a\ndeny-list missed them on a live node before release. A new test makes every migration's\ntable either backed up or named as left out.\n\n**Discover** (ROADMAP row 17). ✦ beside ＋ on every reading screen opens the blygs listed\non blygger.com, read from the browser through blygger.com's `/blygs.json`: *new* (listed\nsince you last looked) or *all*, most active first, each with its activity level and last\npost, a *preview ↗* link that opens the blyg in a new tab, and whether you already follow\nit. Subscribe one at a time or tick several; both go through the OPML import's paced walk\nwith `backfill: false`, and stay out of the blogroll unless the box is ticked. Your own\nblyg is never offered. \"New\" is one timestamp, the newest listing date shown, in the new\n`discoverSeenAt` setting.\n\nPrivate contract 5.9.0, SDK 0.15.0 (`discoverSeenAt`). **Migrations:** none.\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.60.0: Download a backup, discover blygs</h1>\n<p><em>Released 2026-11-14, the reference client. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.60.0\">v0.60.0 on GitHub</a>.</em></p>\n<p><strong>Download backup</strong> (ROADMAP row 15). More → <em>download backup</em> streams the whole blyg as\none <code>.tar</code> from <code>{studio}/backup</code>: every database table as JSON lines under <code>tables/</code>,\npaged so no table is held in memory, every uploaded file under <code>media/</code> by its storage\nkey, a <code>README.txt</code>, and <code>backup.json</code> last, naming the client, the latest applied\nmigration and the counts, with <code>complete: true</code>. A backup without <code>backup.json</code> did not\nfinish. Plain tar, since media is already compressed. The owner's browser session only,\nnever a delegated token. Left out: the OAuth and security tables (grants, tokens, signing\nkeys, rate-limit budgets), wrangler's migration ledger and the feed cache. Restoring one\ninto a fresh node is row 53 and not built.</p>\n<p>The button is marked beta: it runs inside one Worker request, which caps storage reads,\nso on a blyg with very many files it can stop partway (and then has no <code>backup.json</code>).\nFor those, <strong><code>npm run backup -- --base https://your.blyg/ [--env NAME]</code></strong> makes the same\narchive from a deployment checkout through <code>wrangler</code>, one request per table page and per\nfile with retries, so the cap does not apply; a large blyg is only slower. It uses your\n<code>wrangler login</code> session and the deployment's wrangler config. <code>npm run export</code> is still\nthe public site only, for moving to a static host, not a backup.</p>\n<p>Tables are copied by allow-list. The auth library makes its own tables at runtime\n(<code>session</code>, <code>jwks</code>, <code>oauthAccessToken</code>, <code>user</code> and kin), outside <code>migrations/</code>; a\ndeny-list missed them on a live node before release. A new test makes every migration's\ntable either backed up or named as left out.</p>\n<p><strong>Discover</strong> (ROADMAP row 17). ✦ beside ＋ on every reading screen opens the blygs listed\non <a href=\"http://blygger.com\">blygger.com</a>, read from the browser through <a href=\"http://blygger.com\">blygger.com</a>'s <code>/blygs.json</code>: <em>new</em> (listed\nsince you last looked) or <em>all</em>, most active first, each with its activity level and last\npost, a <em>preview ↗</em> link that opens the blyg in a new tab, and whether you already follow\nit. Subscribe one at a time or tick several; both go through the OPML import's paced walk\nwith <code>backfill: false</code>, and stay out of the blogroll unless the box is ticked. Your own\nblyg is never offered. &quot;New&quot; is one timestamp, the newest listing date shown, in the new\n<code>discoverSeenAt</code> setting.</p>\n<p>Private contract 5.9.0, SDK 0.15.0 (<code>discoverSeenAt</code>). <strong>Migrations:</strong> none.</p>\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:f56eaaaa646c17b33baa43fb774f3dcb977dedd6c53a1eab745b2c90160d0190","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-15T05:15:58Z","note":"Studio 0.60.0 released."}]}