Blygger Studio 0.52.0: Collection read batches and smaller Mentions loads
Released 2026-11-04, the reference client. v0.52.0 on GitHub.
Mentions opens with 10 groups and 10 receipts per group. Each list keeps its own cursor and full counts. Corrected page sizes avoid extra continuation requests, and simultaneous freshness checks share one pending read.
Studio batches independent reads by collection operation while retaining the existing endpoints, query validation, permissions, and work budgets. Each child keeps its own status and retry hints. Within each server read batch, ready SQL and admission statements share D1 calls without a timer window or query rewrites. Logical read charges stay unchanged. Batch results are not cached, and a mutation starts a fresh revision check.
Browser batches dispatch in microtasks, so they do not wait for timers that can be throttled in background tabs.
The group query aggregates counts and uses indexed winner lookups instead of ranking every receipt with window functions. No rollup table or trigger is added.
Private contract 5.3.0 (additive POST /read-batch); SDK 0.9.0.
Protocol version unchanged ("0.4").
Subscribing to a collection no longer needs your own collection feeds on
(Aneesh Sathe, #112). Pasting the page or feed URL of another blyg's public
collection now proposes a collection subscription on every node; the
hopper_feeds setting governs only publishing this node's own collection feeds.
API clients that want the whole blyg send wholeBlyg: true.
Two lookups no longer read whole tables (#113, reported by patwater). Resolving an imported item by id alone, and listing each reading entry's collections, each scanned a table on free-plan D1, where the reads count against a daily limit. Both now use an index. (The reader inbox's own ordering index shipped in 0.49.12; nodes older than that should upgrade for it.)
Migrations: 0040 (one covering expression index on mentions_in) and
0041 (indexes on imported_items(remote_id) and hopper_items membership).
Indexes only. Apply before deploying.
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.