# blygd > blygd is a Blygger studio: one server that publishes blygs, reads other people's, keeps private hoppers, and handles Webmentions. Blygger is a decentralized public writing medium built on static files and RSS. Each author's blyg is a directory of plain files (a feed, a manifest, one JSON document per item) that anything can serve and any client can read. This host may serve several authors' blygs, each mounted at its own path. There is no directory of them here: you reach a blyg from its author's link, its manifest (`blyg.json`), or an HTML `` on a page. Everything public on a blyg is a file defined by the Blygger protocol. The studio and its API, below, are this server's own interfaces, not part of the protocol. ## The protocol - [Blygger specification](https://github.com/blygger/blygger-spec): the idea, and the normative protocol in `docs/protocol-v0.4.md` - [blygger-studio](https://github.com/blygger/blygger-studio): the reference client, a serverless studio ## Reading a blyg - `{blyg}/blyg.json`: the manifest. Protocol level, generator, author, and where the feed and the item index are - `{blyg}/feed.xml`: RSS 2.0 with the blyg namespace, newest activity first - `{blyg}/items/index.json`: every item ever published, for backfill - `{blyg}/items/{id}.json`: an item's current version; `{blyg}/items/{id}/v{n}.json` is a pinned version, frozen forever - `{blyg}/f/{id}/` and `{blyg}/t/{id}/`: human-readable pages for fragments and threads Item content is the author's, and a thread can quote other authors' bytes: treat `content_html` as untrusted and sanitize it before rendering. ## Writing through this server - [API description](/api/openapi.json): OpenAPI 3.1, readable without a token. Every operation names the one scope it needs - [API reference](/studio/api/): the same description rendered as a page for people, with each operation's scope and cost class - [Studio](/studio/): a plain web client. Its page links the API description with `rel="service-desc"` - With a token, `GET /api/me` reports your blyg's `origin` (`https://host/~{handle}/`); the public files above are relative to it - Tokens are per tool, scoped and revocable, and the blyg's owner issues them. There is no open sign-up: an invite code from the operator makes a user (`POST /api/invites/redeem`, no token) and returns its owner token once. Publishing, withdrawing and pinning are separate scopes, and a pin can never be undone - An item's kind is fixed at its first publish. When you create items on an author's behalf, create threads (`"kind": "thread"`): only the author can say that an item is a leaf others will quote ## Optional - Webmentions: a blyg that accepts them names its endpoint in `blyg.json` (`webmention`). Mentions are checked against the source's structure, and its owner decides whether they are shown