zat.dev / zat
atproto utils for zig zat.dev
atproto sdk zig
26
fork

Configure Feed

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

zat / docs / roadmap.md
at codex/xrpc-errors-retry 2.6 kB view raw view code
zzstoatzz freshen docs site: inline nav, theme toggle, updated roadmap
866557e7

roadmap#

zat started as a small set of string primitives for AT Protocol — the types everyone reimplements (Tid, Did, Handle, Nsid, Rkey, AtUri). the scope grew based on real usage.

current status#

v0.3.0-alpha — zig 0.16, std.Io throughout.

the v0.3.0 migration replaced all networking and concurrency primitives with zig 0.16's std.Io interface. the API change is mechanical: every networking type takes io: std.Io as its first parameter. streaming clients moved from connect() + next() loops to subscribe(handler) with automatic reconnection, backoff, and host rotation.

the library is stable and tested. the alpha tag reflects that downstream consumers (zlay, labelz, pollz) are still validating in production.

history#

what grew from usage:

  • string primitives with parsing and validation — the initial scope
  • DID/handle resolution — DidResolver, DidDocument, HandleResolver
  • XRPC client and JSON helpers
  • JWT verification for service auth
  • jetstream client — typed JSON event stream with reconnection (v0.1.3)
  • firehose client — raw CBOR event stream, DAG-CBOR codec, CAR codec, CID creation (v0.1.4)
  • MST, ECDSA signing, did:key construction, multibase encoding (v0.1.9)
  • full repo verification — end-to-end trust chain from handle to MST root CID match (v0.2.0)
  • CID hash verification in CAR parser (v0.2.1), size limits (v0.2.2)
  • OAuth 2.1 DPoP client (v0.2.14)
  • configurable keep-alive, transport options (v0.2.12–v0.2.18)
  • std.Io migration, subscribe(handler) streaming API (v0.3.0-alpha)

this pattern — start minimal, expand based on real pain — continues.

what's next#

the library covers the full AT Protocol verification pipeline: identity resolution, repo parsing, signature verification, and MST validation. benchmarked against Go (indigo) and Rust (rsky) in atproto-bench.

near-term:

  • promote to v0.3.0-beta once production consumers stabilize
  • cut v0.3.0 when the API surface is confirmed

what's missing will show up when people build things. until then, no speculative features.

maybe later#

these stay out of scope unless real demand emerges:

  • lexicon codegen — probably a separate project
  • higher-level clients/frameworks — too opinionated
  • token refresh/session management — app-specific
  • feed generator scaffolding — each feed is unique

non-goals#

zat is not trying to be:

  • a "one true SDK" that does everything
  • an opinionated app framework
  • a replacement for understanding the protocol