relay.klbr.net at a really solid coverage at the last eval

new relay up on relay-eval.waow.tech 💫

relay.klbr.net by @klbr.net | @ptr.pet

tangled.org/zzstoatzz.io...

so.... *sigh* back to a thread per PDS for now. we'll try again later. at least its stable on 0.16 now

well: 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

ty for all the improvements 🙇🏻

(i don't think anyone [besides me] is consuming this instance for anything important [probably wise!], but pls lmk if something seems goofy! still tweaking as things come up)

the full migration write-up (nine crashes, cross-Io debugging, a websocket bug masquerading as a fiber bug) is laid out by the latest devlog entry: zat.dev/#devlog/008-the-io-migration.md

and zat.dev got a fresh coat of paint / better mobile support!

2. zig 0.16 (dev)! in particular zlay now uses an evented backend (instead of threaded) based on the new Io interface — it runs ~2,800 PDS subscriber fibers on ~47 OS threads (instead of OS thread per PDS). seems to idle at about ~1.5 GiB RSS and ~1 core... (~20% less mem) still watching things.

1. CBOR/CAR/MST correctness hardening by @calabro.io (i believe i managed to preserve authorship on your commits, ty!) — so RFC 8949 compliance, overflow-safe arithmetic, map key validation, UTF-8 checks.

frame decode throughput drops from ~290k to ~202k fps (but is still 13x faster than indigo)

nice clouds

zlay.waow.tech has been running (mostly) smoothly on zat v0.3.0-alpha.21 for coming up on a day! this is significant for 2 reasons

relay-eval comparing what each atproto relay sees

tinkering w something inspired by @mackuba.eu 's pulsar.feeds.blue

relay-eval.waow.tech

hrm i might be letting through a few DIDs i should not be (which may explain the extra couple hundred users) ... *buffering*

pulsar.feeds.blue

zlay on ze top of pulsar.feeds.blue

zlay day 2day 👁️

at first i thought of it as zee-lay but i have since succumbed to zlay 💅

yass, we are climbing pulsar.feeds.blue

zlay.waow.tech is on the board!

(a relay written in zig [with zat] that has collectiondir support)

WARNING challenger approaching thing from melee

zlay.waow.tech

https://atproto.com/sdks

hi mom from atproto.com/sdks!

new in 0.2.0 — ECDSA signing, MST, did:key construction, and correctness fixes from running against the interop test files: github.com/bluesky-social/atproto/tree/main/interop-test-files

read the changelog: zat.dev#changelog.md

now in 0.1.6 — firehose/jetstream clients round-robin across multiple hosts on reconnect, including community relays (waow.tech, fire.hose.cam, firehose.stream, firehose.network)

zat.dev#changelog.md

zat has been moved to a tangled.org repo under this account

also, zat.dev is now a @standard.site!

atproto records: at-me.zzstoatzz.io/view?handle=...

read more: zat.dev/#devlog/001-self-publishing-docs.md

yay! we are socially coding on @tangled.org - ty @seiso.moe :)

tangled.org/zzstoatzz.io...

yay!

DoH! cool!

u plan to push that anywhere>

hello world!

zat is a minimal zig atproto sdk

readme + roadmap are on @wisp.place at zat.dev

docs are updated on push to main by this tangled workflow

tangled.org/zzstoatzz.io...