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/.

Tangling: write the essay, publish the parts

Blygger Studio 0.63.0 adds tangling. You write one piece, mark the passages that can stand on their own, and publish once. Each marked passage becomes an item of its own, with its own page, history and feed entry. The piece you wrote becomes a thread that quotes them, so it reads exactly as it did.

Why

A blyg is made of small pieces that quote each other. A fragment can be cited, quoted in someone else's thread, and pinned at a version. That is the medium's strength. It is also a discipline most writers do not have. Nobody sits down to write a commonplace book of standalone claims. People write essays, and only afterwards notice which paragraphs were the ones worth keeping.

Until now, getting those paragraphs out meant doing it by hand: copy the passage into a new item, publish it, and go back to replace the passage with a quote. Tangling does that bookkeeping for you. The name comes from Knuth's literate programming, where one document "tangles" into the separate pieces a machine needs. Here the machine is the reader, and the pieces are the parts of your argument that other people will want to point at.

How it looks

Mark a passage with ![[+ and ]]:

Most of what we call infrastructure is invisible until it breaks.

![[+ Stigmergy is the mechanism by which a protocol becomes invisible
to the people inside it. The trail tells you where to go, and you
stop noticing that someone laid it.]]

That is why protocol failures feel like betrayals rather than accidents.

The preview shows the marked passage as a dashed quote, so you can see what will become its own item. When you publish, the studio counts first: "This will publish 1 new item and this thread." Nothing is created until you choose publish all. Then the new item is published, then the thread, and the thread's source is rewritten to an ordinary quote of the new item:

![[k3v9… | Stigmergy is the mechanism by which…]]

From there on it is a normal quote. Edit the new item and the thread can pick up the edit like any other quote. Delete the quote from the thread and the item stays published.

A single publish can mark up to ten passages. If any of them would fail to publish, or the thread itself would, nothing is created at all. If the publish stops part way, for example because the connection drops, the next publish finishes it.

Placeholders: the ideas you haven't written yet

The same release adds a smaller relative. [[+ text]] inside a sentence, without the !, marks an idea you mean to come back to:

This connects to [[+ the economics of trail maintenance]],
which deserves its own post.

Publishing makes a new thread whose text is just that phrase, as a heading, and turns the phrase in your sentence into a link to it. The new thread's working copy carries a private note saying which thread and which sentence it came from, so that when you come back in a month you know why it exists. Notes like that are comments to yourself and are never published. Later you open the placeholder, write the post, and publish again. Everyone who followed the link now finds the real thing at the same address.

Some ways to use it

  • Essays that yield quotable claims. Write the argument end to end, then mark the three or four sentences you would want someone to quote. Each gets a stable address that a reply can cite.
  • Definitions in a longer piece. Mark each term's definition where it first appears. Your later writing, and other people's, can quote the definition instead of restating it.
  • Meeting or reading notes. Write the notes as one document and mark the decisions or the passages worth keeping. The notes stay as the record, and each decision becomes something you can link to.
  • Outlining forward. Write the overview and use placeholders for the sections you haven't written. The overview publishes now, with working links to each section's future home.
  • A book's chapters. A contents page can link chapters written separately, and a chapter can be drafted as one long piece and tangled into sections.

What your readers see

One act of writing now produces several items, and every item is a real publication with its own feed entry. The spec has no quiet publish, because a publish the feed leaves out is hidden from subscribers. Without care, one tangled essay would arrive as half a dozen separate entries in a reader's feed.

So readers fold them. Blygger Studio's reader shows the thread as one entry, marked +N parts, and moves the parts it quotes into Background, where they can still be opened and nothing is lost. Placeholders fold the same way, but only when they say nothing beyond the link's own words. A chapter that a contents page links seconds after it was published stays its own arrival. The rule for that last case was settled the day 0.63.0 shipped, in the eighteenth revision of the spec, §13.7.

None of this needs anything new on the wire. The ![[+ …]] and [[+ …]] forms are the studio's own authoring syntax and are rewritten before anything is published. A blyg reading yours sees ordinary items and an ordinary thread that quotes and links them, plus links[], which 0.63.0 also starts to publish. Any client can fold a burst from what is already in the item documents.

Try it

Tangling is in Blygger Studio 0.63.0, live on blyg.blygger.org, venkateshrao.com/blyg and blyg.protocol-institute.org. The syntax page in the studio (more → syntax) has both forms. If you run your own node, npm run upgrade brings it in, along with two migrations. The design is in docs/tangling-plan.md, and the history of the idea is on blygger-studio#20.

Source: docs/posts/2026-11-18-tangling.md in blygger-spec, which is where revisions are made. To comment, respond to this item from your own blyg.

Created: Nov 19, 2026

Responses