RSS ⧉

Blygger

Venkatesh Rao

The official blyg of the blygger protocol: RFCs open for comment, release announcements from every client, and technical notes. The spec itself lives at blygger.org/spec/.

The day in Blygger, 19 October 2026: links that notify, reposts as notices, and two-way quotes on your own blyg

Protocol 0.4 took its fourth revision, now live on blygger.org, with five new decisions, #79 through #83. They started from one observation: there is demand for simple responses. Blygger Studio 0.48.0 shipped the same day with nine contributor pull requests, among them Kyle Mathews' fix for mentions showing up out of order, and two new features of its own: your own posts can be stubbed from the reading feed, and every public page now lists the posts on the same blyg that quote it.

Blygger Studio 0.48.0

Released 2026-10-19, the reference client. v0.48.0 on GitHub.

Migrations: 0028, 0030, 0031, 0032 — apply them before deploying (wrangler d1 migrations apply DB --remote). 0031 backfills version_media so no live document changes at upgrade. Optional new secret TYPESAFE_API_KEY, needed only to use Jev as the change classifier. Implements protocol 0.4.

  • Own items in the reading feed get stub ↗, add to hopper and fork (Venkat). Your own entries offered only edit and link post. A stub of your own post quotes its live version and cites it with a same-origin stub_of, which sends no mention (§15.2); a withdrawn post is cited without a quote. The lineage sheet now offers these actions on your own posts and says what differs.
  • Local mentions on public pages (Venkat). A fragment or thread page lists this blyg's own published items that stub, quote or fork it, each linked back, so a transclusion is walkable in both directions on your site. Like Responses it is page chrome, never in a document, feed or hash; unlike Responses it needs no opt-in, because every row is your own. Only live versions count: a quote edited out, or a withdrawn quoter, leaves the list.
  • Attachments per version (studio#7, Aneesh Sathe; migration 0031). Each published version records the attachments it showed. Removing an attachment drops it from the next version only; earlier versions keep listing it and its bytes keep serving. Before, an attachment appended below a post could have its bytes deleted while a published version still listed it.
  • Duplicate uploads return the existing file (studio#7, Aneesh Sathe; migration 0028). The same bytes, type and placement on the same item store nothing new; POST /api/media answers 200 with duplicate: true.
  • Optional change classifier (Aneesh Sathe; migration 0030). Off unless Settings → AI → change classifier names a decision model (Clef or Clef-flash on Workers AI, or TypeSafe's Jev). It suggests typo, minor or major for a new version in the publish dialog, refresh for a republish of the same words with no model call, and can lead the change note with that word. The label is kept privately with the version; readers see it only as words in your note, and no client gives it meaning (decision #83).
  • OPML import (studio#63, Aneesh Sathe). Import subscriptions from an OPML file in Sources, with a preview, per-feed choice, an optional add-to-blogroll, and a per-row result. Imported feeds are fetched by the next background poll.
  • Mentions show up as they arrive (Aneesh Sathe; migration 0032). Verified responses, and hiding or showing one, now refresh the public page at once instead of after the edge cache expired (up to about six minutes), and the studio's mention views re-read only when something changed.
  • Newest Webmention responses first (Kyle Mathews). Response groups on the Webmentions page had come back in random id order.
  • Label grammar: six edge cases fixed (#70, Aneesh Sathe), found porting the renderer to another client, among them a label escaped twice inside a generated block and a backtick in one label disabling a later link.
  • Studio on the phone (Aneesh Sathe): no more random zoom on iOS (fields under 16px, double-tap), compact reading cards, full-screen reading, and a quieter composer and editor.
  • TanStack DB packages updated (Kyle Mathews).

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.

thread ↗ · snapshot of v1

The rulings

  • Links notify (#79, reversing #32). A resolved [[id]] now goes on the wire as an entry in a new links[] array: {id} for your own items, {id, origin} for another blyg's. A link names a page, not a version, so an entry carries no version and no citation. A remote entry SHOULD send a mention, and the receiver records a fifth relation, link. The silent citation survives as the plain markdown link [text](url), which nobody inspects. You choose by how you write the link. (§10.3a)
  • Reposts are notices (#80). A bare ![[id]] is not discouraged: it is the reference client's repost shape. The receiver takes the fetched document, strips directive lines, attached passages, labels and whitespace, and if nothing is left, it is a repost. No marker is added; the wire already says it. Verified mentions now come in two classes: responses (stubs, quotes, forks and sources, with words of their own) and notices (links and reposts). Notices never appear in a responses list. (§15.4, §15.5)
  • The quote's label travels (#81). The label in ![[id | text]] is now baked onto the quote as data-blyg-label, and is RECOMMENDED as the text of the "quoted from" line, so subscribers and forks see it too. It is the quoter's words about the target, never the target's title.
  • Respond from anywhere (#82). Quoting and stubbing no longer need a subscription. The old rule, "from any subscribed origin", was a client-local notion that had leaked into the wire. Any snapshot a client holds from the item's own origin will do, whether it was polled or fetched once. The recommended client shape is a deep link that takes any URL, so a bookmarklet, the share sheet or a browser extension can open the stub composer. A "stub this" button on every blyg page has to work across clients, so it goes to an RFC first: RFC-4, now being drafted. (§16.11)
  • No significance token (#83). A changelog note may say a change is minor, in words; that is what the note is for (TN-1). But no word in a note has wire meaning, and no client may give one any. A token that readers route on is the "this matters less" flag already refused, with a worse spec: [skip ci] is the precedent, and its own attack is softening a strong claim under the token so subscribers don't re-read it. The author's lever is not publishing a change that isn't worth an event. Readers get near-sameness instead: a version whose text barely differs from the one before it MAY be queued as maintenance, by a threshold each reader keeps to itself.

If you run a blyg

  • Blygger Studio 0.48.0. Apply migrations 0028, 0030, 0031 and 0032 before deploying.
    • Stub your own posts. Your own entries in the reading feed get stub ↗, add to hopper and fork. A stub of your own post quotes its live version and cites it on the same blyg, so no mention goes out.
    • Local mentions. Every fragment and thread page lists the posts on the same blyg that stub, quote or fork it, each linked back. Together with the "quoted from" line a quote already carries, a quote can now be followed in both directions on your own site. Like Responses, the list is page chrome, never part of an item document or feed. Unlike Responses it needs no opt-in, because every row is yours.
    • Attachments per version (Aneesh Sathe). Removing an attachment drops it from the next version only; earlier versions keep showing it. Uploading the same file twice to the same post stores it once.
    • An optional change classifier (Aneesh Sathe), off by default. A cheap decision model (Clef on Workers AI, or TypeSafe's Jev) suggests typo, minor or major for a new version, and can lead your change note with that word. Under #83 it is prose: your words, which readers may read and no client acts on.
    • OPML import (Aneesh Sathe), with a preview, a choice per feed, and an optional add-to-blogroll.
    • Mentions in the right order (Kyle Mathews, studio#76). The studio's Webmentions page groups mentions by the post they answer, and the groups came back in random order, because mention ids are random. A response that had just arrived could sit below months-old ones and look as if it had not arrived at all. Kyle rewrote the page's query as a TanStack DB live query: groups sort by their newest verified mention, and their counts and visibility are computed in the same query. An oracle test checks it against an independent model, and mutation checks reject any broken ordering or visibility. Delivery and verification were never at fault; only the view was.
    • Responses appear at once (Aneesh Sathe). A newly verified response, or hiding or showing one, used to take up to six minutes to reach the public page.
    • On the phone (Aneesh Sathe): no more random zoom on iOS, compact cards and full-screen reading.
    • Six edge cases in the 0.47 label grammar fixed, found by Aneesh while porting the renderer to another client.

If you write a client

  • Build to the fourth revision. The changes on the wire are small and additive: links[] on item documents and data-blyg-label on the quote blockquote. A 0.3 reader ignores both. The rest is receiver behaviour: the link relation, the repost test, and keeping notices out of responses lists.
  • Never parse a change note (§5.2), and treat near-sameness as your own reader-side choice: keep the threshold small, since one word can negate a sentence, and never omit a version, only queue it.
  • Respond from any URL. If your client can fetch an item's document once, it can let its author stub it. RFC-4 will settle how a page offers that across clients; until it publishes, please don't add a "stub this" link to public pages.

Next

The reference client builds the rest of today's rulings: disclosed links with "linked this" lines in local mentions, the repost test, the traveling label and near-sameness, then a plan for stubbing from any URL and the RFC-4 draft. RFC-1 and RFC-2 are open for comment here until 4 November.

Created: Oct 20, 2026