Blygger Studio 0.39.0
Released 2026-10-09, the reference client. v0.39.0 on GitHub.
Migrations: 0026_read_state.sql (a read_state table and five triggers).
Apply it before deploying: wrangler d1 migrations apply <database> --remote.
- Read state for imported items (Aneesh Sathe, #44 and #45). Reading entries show an unread dot. Opening an entry marks it read, and a select mode marks several read or unread at once, or the whole feed read. Read state is stored per imported item with the version you read, so a new version of an item shows as unread again. Marking unread leaves a tombstone, so a stale "read" from a client that was offline cannot undo it. It stays in the studio: nothing about it reaches the feed, the item documents or other blygs.
- API:
PUTandDELETE /api/reading/{sub}/{remoteId}/read, the batch routesPOST /api/reading/readandPOST /api/reading/unread(up to the batch limit in one write), andreadVersiononGET /api/reading. A change advances thereadingrevision inGET /api/changes. Read state is deleted along with its imported item or subscription. - A new scope,
reading:state, for marking read and unread. A reader app that only syncs read state does not needowner:manage, which can also delete subscriptions, andowner:managedoes not include read state. Existing grants are unchanged; a client that wants read state asks for the new scope.
This announcement is drafted from the release's section of CHANGELOG.md, which is where it is maintained. To comment, respond to this item from your own blyg.