~/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.4) 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).
  • A 60-second public page cache (#41; 0.33.0), Webmention delivery for long subscription origins (#42), and shared source schemas (#43).
  • Led the 0.49 API cleanup, eleven pull requests tracked in #92: the private API under the deployment mount, conditional item writes, bounded cursor pages, media addressed by digest, complete HTTP validators, and one set of operations shared by REST and MCP (0.49.1–0.49.12).
  • Kept Studio fast as blygs grew: optimistic writes and paged mentions, batched collection reads, and read batches that survive malformed paths (#111, #114, #116); SQLite full-text search is in review (#146).

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): 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. Since extended to 0.4 with a reader suite: 100 fixtures, written from the spec text, that any client's renderer can run (blygger-spec#22), and kept current with the spec's revisions (blygger-spec#33, in review).
  • Issues across the spec and Studio: 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).
  • Fixes the suite turned up, built in Studio: partial quotes that take CommonMark's blockquote extent, own-line quotes in generated output, the directive label baked as the quote's attribution, and hopper subscriptions (#106, #107, #136, #112). The Shelf and syndication are in review (#137, #148). 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).
  • Studio's extension mechanism (#52), with Aneesh's lineage glyph and hex view as the first extension (#53).
  • Read state for imported items, OPML import and attachments per version (#44, #74, #80), and the proposal that made public hoppers subscribable (blygger-spec#18, ruled as decision #86).

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

Contributors

  • akash — @akashtattva. The mobile navigation and Contents drawer on this site (blygger-org#1), and blyg feeds that strict RSS readers accept (blygger-studio#33), and an SDK build that works on Windows (#89).
  • Robert Peake — @cyberscribe. Proposed that the manifest say where the rest of a blyg lives, so sites that cannot follow the file layout — WordPress, for one — can still publish one (blygger-spec#2). Ruled in as decision #51; part of 0.4. Also found that the Webmention target check excluded pages and item documents that 0.4 lets live outside the base URL (blygger-spec#17, decision #84).
  • Brady Dale — @BradyDale. The robot badge that discloses generated text began as a convention on bradydale.com; Studio adopted it in 0.27.0.
  • Anuraj R — @anuraj-rp. An RFC for an optional content identifier on pinned versions, for mirroring pins to IPFS (blygger-spec#13).
  • Matthew Sweet — @msmsim. A proposed extension for Glass Bead Games (blygger-spec#12).
  • Mike Casey — @miguelito4. A custom theme with live preview and a reading typeface for Studio (blygger-studio#58).
  • Raynaud Simon — @keyral. Reported broken links in the spec's docs (blygger-spec#3).
  • djinna — @djinna. Asked for a way to size inline images (blygger-studio#37).
  • Surya Kasturi — @ksurya. Asked for passkeys and a discard-draft button, and reported what it takes to put a blyg's MCP server behind Cloudflare's MCP portals (blygger-studio#50, #54, #56); reported that Webmentions could be used to flood a node (#72); asked for every endpoint under the mount (#70) and for stubbing without subscribing (#83).
  • Ned Twigg — @nedtwigg. Asked for comments inside transcluded ids (blygger-spec#16), which became the [[id | label]] form (decision #70), and for tooltips in Studio (blygger-studio#48).
  • Florian Lohse — @florianlohse. Moved a blyg to a new origin, and filed the issue that turned moving into a rule, origin succession (blygger-studio#102, decision #88).
  • Rafael David — @rafaeldavid. Four reviews of the HTTP and agent-facing surface: validators and immutable pins (blygger-studio#87), fetched text as data for agent readers (blygger-spec#19), published JSON Schemas (blygger-spec#20), and soft 404s on this site (blygger-org#4).
  • Shannon — @shannonbux. Studio's controls moved onto shared Base UI primitives, with a component gallery (blygger-studio#88, in progress).
  • Ruthvik Peddawandla — @ruthvik-947. The nodejs_compat flag in the config npm run init writes (blygger-studio#46).

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.