atproto relay implementation in zig zlay.waow.tech
9
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: add getHostStatus to endpoint list, drop fan-out contrast

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

zzstoatzz e7688366 4b9b4295

+2 -3
+2 -3
README.md
··· 6 6 7 7 ## design 8 8 9 - - **direct PDS crawl** — the bootstrap relay (`bsky.network`) is called once at startup for the host list via `listHosts`, then all data flows directly from each PDS. no fan-out relay in between. 9 + - **direct PDS crawl** — the bootstrap relay (`bsky.network`) is called once at startup for the host list via `listHosts`, then all data flows directly from each PDS. 10 10 11 11 - **optimistic signature validation** — on signing key cache miss, the frame passes through immediately and the DID is queued for background resolution. the first commit from an unknown account is unvalidated; all subsequent commits are verified against the cached key. >99.9% cache hit rate after warmup. 12 12 ··· 24 24 | `com.atproto.sync.getLatestCommit` | GET | 25 25 | `com.atproto.sync.listReposByCollection` | GET | 26 26 | `com.atproto.sync.listHosts` | GET | 27 + | `com.atproto.sync.getHostStatus` | GET | 27 28 | `com.atproto.sync.requestCrawl` | POST | 28 - 29 - `getRepo` is not implemented — the relay does not serve full repository exports. 30 29 31 30 ## dependencies 32 31