Reposted by zatfig (aka:[phil]) @bad-example.com · 16/09/2026what's an atproto app that consumes the firehose (not jetstream) or otherwise handles CARs? i have surveyed 10 and my 5-emoji split in three categories needs a tiebreaker. 5191
Reposted by zatcove.town @cove.town · 31/08/2026cove.town is an experiment in self-hosting @atproto.com based services, including a knot, spindle, hold, and a PDS. You're welcome to use the container images, and feel free to fork the repo as a starting point to set up your own stack.cove.towncove.townA PDS, a knot, a spindle, and a hold, atproto infrastructure fully built on itself. 0179
zat @zat.dev · 28/08/2026all good! it helped me find an inefficiency in the pds implementation :) 010
zat @zat.dev · 28/08/2026hey @jesseplusplus.com ! fwiw pds.zat.dev supports com.atproto.space.registerNotify, ie register a service endpoint and it'll push you notifyWrite calls when a space changes, instead of polling listRepos. (note registration expires, so renew before expiresAt) happy to share notes/further detail! 100
zat @zat.dev · 20/08/2026btw don't sleep on @chadtmiller.com tangled.org/chadtmiller.... the madman migrated his main 120
Reposted by zatP(aul) Frazee @pfrazee.com · 18/08/2026It's been so nice to see people posting about picking up the new jetstream. @calabro.io put in serious hours on it, and lots of the team pitched in to reach the finish line, and it means a lot that folks are sharing about it now. Long project like that, good to have a gratifying ending. 2793
Reposted by zatJim Calabro ♟️ @calabro.io · 13/08/2026Do you like fast network replay? How does ~40 million events per second strike you? Replay the whole network in like 10 minutes In the best case scenario, running the jetstream server and the client on your own very powerful machine, this is roughly the peak I've achieved so far 1016025
zat @zat.dev · 12/08/2026current consumers include: - @plyr.fm - @find-bufo.com - coral.waow.tech summary of the port: claude.ai/code/artifac... 030
zat @zat.dev · 12/08/2026stream.waow.tech is a jetstream v2 instance written with tangled.org/zat.dev/zatstream.waow.techstreamjetstream v2 firehose + full-network atproto archive · network seq 32,676,919,468 · 6,614 sealed segments 2150
Reposted by zatfig (aka:[phil]) @bad-example.com · 05/08/2026HANG ON we hit THREE THOUSAND pdses this week?? 3k pdses in the atmosphere! 514117
zat @zat.dev · 05/08/2026yesterday's crashed was caused by a bug in zio (the fiber-based std.Io implementation that avoids naive threading per PDS host)tangled.orgbackend: round sub-millisecond sleeps UP so they actually park · zzstoatzz.io/zio@d5c0a2eA repository on Tangled 000
zat @zat.dev · 05/08/2026ok actually this time i think relay-eval.waow.tech/chart?range=... zlay-metrics.waow.tech/goto/afuasr3... 100
zat @zat.dev · 04/08/2026ope! something got wedged, rolling back and looking something something counting chickens 000
zat @zat.dev · 23/07/2026more considerations on the docket: float64 DRISL, malformed/missing seq, missing record blocks, record-shape validation, and the signing-key cache fail-open window s/o @ptr.pet for hydrant and for pushing us forward! 140
zat @zat.dev · 23/07/2026speaking of conformance: since eli made the table, zlay became more strict and flipped some cases from ACCEPT → REJECT: CAR CID mismatch, wrong-key commits, wrong-key syncs, missing and/or incorrect prevData instance updated and healthy at zlay.waow.tech 130
zat @zat.dev · 05/07/2026zat v0.3.11 is out now - mostly small improvements zat.dev now displays 5 practical examples: zat.dev#examples/ind... read the changelog: zat.dev#changelog.mdzat.devzat.devAT Protocol building blocks for zig 181
Reposted by zatVanilagy @vanilagy.bsky.social · 29/06/2026Introducing TurboRes, an extremely fast ProRes video decoder for the web! 🚀 Written from scratch in Zig and compiled to WebAssembly, TurboRes has been relentlessly optimized for performance and is around 2-3x faster than native FFmpeg. 3535
Reposted by zatgarrison @garrison.corporate.fm · 23/06/2026appreciate mitchell's words here, imo it's good to have communities and projects that abstain from llm use and I think the zig project has great principles mitchellh.com/writing/zig-...mitchellh.comPledging Another $400,000 to the Zig Software Foundation 043
zat @zat.dev · 12/06/2026pds.zat.dev now uses @comail.at for account verification emails :) see details: tangled.org/zat.dev/zds/... 180
zat @zat.dev · 09/06/2026"i am colorblind" is my imagined one-size-fits-all cop out for negligence that can be feasibly blamed on poor eyesight (i notice contrast or lack thereof yes) 140
zat @zat.dev · 03/06/2026btw this account lives at pds.zat.dev now!pds.zat.devpds.zat.devan at protocol personal data server 040
zat @zat.dev · 03/06/2026we're actually back! thanks to bsky devs jim/devin and a smol fix to zds tangled.org/zat.dev/zds/...tangled.orgfix sync firehose backfill writes · zat.dev/zds@79b153datproto pds in zig 210
zat @zat.dev · 01/06/2026new in zat v0.3.5: faster MSTs! no breaking changes this release tightens the MST implementation according to lessons from operating relay/PDS in the wild, and further improves insert and lookup throughput read the devlog: zat.dev#devlog/012-m...zat.devzat.devAT Protocol building blocks for zig 000
zat @zat.dev · 28/05/2026zat.dev#devlog/011-b...zat.devzat.devAT Protocol building blocks for zig 010
zat @zat.dev · 25/05/2026v0.3.3 adds jwt.verifyJose — lenient ES256/ES256K, for OAuth assertions and DPoP motivated by the development of tangled.org/zat.dev/zds read the devlog: zat.dev#devlog/011-b... 050
zat @zat.dev · 14/05/2026relay-eval.waow.tech/sonifyrelay-eval.waow.techsonify · relay-evaleach relay's live events/sec mapped 1:1 to a tone in Hz — relays seeing similar event volume converge in pitch 000
Reposted by zatfig (aka:[phil]) @bad-example.com · 11/05/2026kicking off a firehose.club community relay list, thanks to @sri.xyz ! open a PR to add yours!tangled.orgfirehose.club/3ml2fpb5s6w22A repository on Tangled 23610
zat @zat.dev · 08/05/2026ok! i think you helped me expose 2 latent bugs: idiosyncratic silent DB worker death + a stale websocket pin that broke POST-with-body handling. both should be fixed / deployed. i swept through and reactivated your PDS along some similar others! tysm for reporting! lmk if you see further issues! 010
zat @zat.dev · 07/05/2026zat v0.3.1 adds safe identity resolution, checked XRPC errors, retry/rate-limit handling, and refreshed benchmark numbers here's the new devlog entry: zat.dev#devlog/010-t... 060
zat @zat.dev · 17/04/2026new relay up on relay-eval.waow.tech 💫 relay.klbr.net by @klbr.net | @ptr.pet tangled.org/zzstoatzz.io... 2224
zat @zat.dev · 11/04/2026so.... *sigh* back to a thread per PDS for now. we'll try again later. at least its stable on 0.16 now 000
zat @zat.dev · 11/04/2026well: zat.dev#devlog/009-b... had a hell of a bad time operating the evented backend since the 0.16 migration. can't recommend trying to patch stdlib zig's Io_uring in a large scale distributed system you're not totally familiar with. it was alive? but not stable 100