~/blygger.org/contributors/

Contributors

Blygger is built in public, by more people every week. This page credits them in two groups. The first tab is for work on the protocol itself and on the reference client, Blygger Studio: pull requests, bug reports, proposals. The second is for people building their own clients, integrations and tools — the independent implementations that show the protocol works from its spec alone.

Everything here is drawn from the public record: pull requests and issues in the blygger repositories, and the ecosystem index. If you are missing, or described wrongly, open an issue.

Core contributors

Venkatesh Rao — @vgururao

Started the protocol. Author of the specification (0.1 through 0.3) and of the decision log behind it; maintains Blygger Studio, this site, and the blygger.com directory, and runs the first live node at venkateshrao.com/blyg/.

Kyle Mathews — @KyleAMathews

Much of the reference client's current architecture:

  • Rebuilt Studio as a React single-page app on a validated resource API with a generated SDK (#21, #22; 0.10.0).
  • Made the public homepage fast: batched reads and indexed lookups took time to first byte from about 4 seconds to about 0.35 (#25; 0.11.1).
  • Scoped client access with OAuth and MCP, so other software — including AI agents — can work with a node under tokens its owner grants and revokes (#34; 0.28.0).
  • Cut database reads from Studio's polling and the public feeds (#40; 0.32.0).
  • In review: a 60-second public page cache (#41), Webmention delivery for long subscription origins (#42), and shared source schemas (#43).

Runs blyg.bricolage.io.

Aneesh Sathe — @aneeshsathe

The protocol's most thorough reader so far, and the first to test it systematically:

  • A conformance and intent toolkit, with a first-round report (blygger-spec#11, in review): every MUST, SHOULD and MAY in the 0.3 spec indexed, JSON Schemas for every document, a read-only crawler that checks the live network against the spec, and formal models of the rules that turned up gaps worth ruling on.
  • Twenty-three issues across the spec and Studio, seventeen of them fixed: grammar edge cases in transclusion and generation scopes, importer and lineage bugs, and the question that made [[id]] links inert inside code (blygger-spec#4). A suggestion of Aneesh's put public hoppers on pages of their own (0.24.0).
  • Studio redesigned for the phone (#32, #36; 0.22.0).
  • A lineage glyph, hex view and action ring (#35), held as the first candidate for Studio's extension mechanism rather than the base client.

Also builds blygger-desktop (see the ecosystem tab), and runs blyg.aneeshsathe.com.

Contributors

Ecosystem contributors

People building their own clients, integrations and tools, alongside the reference client. The ecosystem page indexes the projects and the live blygs they serve.

Clients known only by their blygs

These publish with clients of their own whose authors haven't been matched to a profile yet. If one is yours, say so.