~/blygger.org/rfcs/
Requests for comments
An RFC proposes a convention or a design that more than one client would follow. Each is published on the official blyg, blyg.blygger.org, with a comment period. Like a technical note, an RFC constrains nothing. When its period closes it becomes a technical note.
To comment, respond to the RFC 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. Without a blyg, comment on the RFC's GitHub issue.
| RFC | Status |
|---|---|
| RFC-7: Payments: one more ground for a grant, any rail at the door | open until 2026-11-28 · GitHub |
| RFC-6: Sealed content and permissions: covers on the wire, keys by lock, grants as files | open until 2026-11-28 · GitHub |
| RFC-5: Blygger inside an organisation: one audience per origin, a boundary the publisher enforces | open until 2026-12-03 · GitHub |
| RFC-3: The pace-layered order: what keeps mattering stays near the top | open until 2026-12-10 · GitHub |
| RFC-2: Comments sections: a curated display of responses, every comment a real item | closed 2026-11-04; now TN-7 |
| RFC-1: Mentions across identifier schemes: petnames in the studio, full identifiers on the wire | closed 2026-11-04; now TN-6 |
Published from blygger/blygger-spec@97c9471.