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
- 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).
- 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 and scheduled for 0.4.
- 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 and reading typeface for Studio (blygger-studio#38).
- 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).
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.
- Brady Dale — @BradyDale. Blynger, an independent client on its own version line, publishing at bradydale.com/blyg.
- Robert Peake — @cyberscribe. Soapbox, a WordPress plugin that publishes a blyg, in progress — the first client built on the manifest-located surface proposed in blygger-spec#2.
- Aneesh Sathe — @aneeshsathe. blygger-desktop, a native macOS studio for blygs in Rust.
- Mike Casey — @miguelito4.
drafts-blyg, one-tap fragments
from a phone via Drafts, and
static-to-studio, which
moves a static blyg into Blygger Studio at the same address. Wrote a static
client,
caseyjr-blyg, before moving caseyjr.org/blyg into Studio with it. - Brandon Pink — @brndnpink. blyg-publisher, an Obsidian plugin that publishes a blyg from a folder of your vault.
- Christopher Boette — @chrisbodhi. hugo-blyg, a blyg from a Hugo site, published at newschematic.org/blyg.
- Mike Travers — @mtravers. Taught goddinpotty, a digital-garden generator for Logseq graphs, to emit a blyg: AMMDI.
- Patrick Atwater — @patwater. pioneering-spirit-blyg, Blygger Studio extended to run Pioneering Spirit beside its old archive, and a Windows port of blygger-desktop.
- Matthew Sweet — @msmsim. msn, an independent client, publishing at msweet.net/notes.
- Protocols for Business — @protocolvision. The Protocol Institute research group's own static client, sig-p4b, publishing at protocolsforbusiness.com/blyg.
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.
- thinking.drwip.com/blyg — the first independent implementation, before the September 2026 talk.
- blyg.sachinbenny.xyz —
sachin-blyg. - artlu.xyz —
astro-gyoza. - florianlohse.com/blyg —
my-garden-site. - rafael.fyi/blyg —
rafael-fyi-blyg, adapted from Protocols for Business's client.