{"blyg":"0.3","id":"13755kpnak744x5cr7n6mqhsza","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/13755kpnak744x5cr7n6mqhsza/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-10-07T20:03:09Z","updated":"2026-10-07T20:13:04Z","version":2,"content_md":"\n# Introducing the official Blygger blyg\n\nThis is the official blyg of the blygger protocol. It sits beside [blygger.org](https://blygger.org/), which keeps the spec, and [blygger.com](https://blygger.com/), the directory of blygs. Anything about the protocol that announces a change or asks for a response is published here, so this is the one place to follow the project from a reader.\n\nWhat appears here:\n\n- **RFCs.** Proposed conventions for clients, published for a comment period before any client builds them, so that a convention reaches the reference client only after other implementers have had their say. Each RFC is a thread, and the version under comment is pinned. To comment, respond from your own blyg: a stub is a comment, a partial quote names the passage you are answering, and a fork of the pinned version is a counter-proposal. Each RFC also links a GitHub issue for anyone without a blyg. The first two cover mentions across identifier schemes and comments sections.\n- **Release announcements from every client.** Releases of the reference client, and of any other blygger client, tool or integration. If you maintain one, open an issue on [blygger/blygger-spec](https://github.com/blygger/blygger-spec/issues) when you ship and the release will be announced here.\n- **Technical notes.** The design reasoning behind the spec, especially the designs it rejected, starting with TN-1 (versioning and pins) and TN-3 (groups). Their canonical text stays at [blygger.org/notes/](https://blygger.org/notes/), which the spec cites; the copies here are where they take responses.\n- **Spec revisions and snapshots**, each announced with what changed.\n\nWhat stays elsewhere: the spec itself, at [blygger.org/spec/](https://blygger.org/spec/), and the reference pages on blygger.org such as the ecosystem list.\n\nOn bylines: most of what appears here is drafted by AI models and approved by Venkatesh Rao, whose name is the byline. Each such item discloses the model that wrote it, as this one does.\n\nTo follow, subscribe to `https://blyg.blygger.org/` from any blyg-aware reader, or add `https://blyg.blygger.org/feed.xml` to an ordinary feed reader.\n","content_html":"

Introducing the official Blygger blyg

\n

This is the official blyg of the blygger protocol. It sits beside blygger.org, which keeps the spec, and blygger.com, the directory of blygs. Anything about the protocol that announces a change or asks for a response is published here, so this is the one place to follow the project from a reader.

\n

What appears here:

\n\n

What stays elsewhere: the spec itself, at blygger.org/spec/, and the reference pages on blygger.org such as the ecosystem list.

\n

On bylines: most of what appears here is drafted by AI models and approved by Venkatesh Rao, whose name is the byline. Each such item discloses the model that wrote it, as this one does.

\n

To follow, subscribe to https://blyg.blygger.org/ from any blyg-aware reader, or add https://blyg.blygger.org/feed.xml to an ordinary feed reader.

\n
\n","content_hash":"sha256:249dd88a964ac9ed598039b3f287b86edb21a41525cd6858eface2899ff9abf0","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-10-07T20:12:37Z","note":"Introducing the official Blygger blyg."},{"version":2,"at":"2026-10-07T20:13:04Z","note":"Markup fix: the post rendered inside a stray inline span."}]}