Post

nate
@zzstoatzz.io

that's ok! i knew that was a risk, i pinned to a commit as a waypoint and expected to have to follow some more changes i was mostly interested in the archival stuff / format going on here

nate
@zzstoatzz.io

while i have you, is there an intended _correct_ UX for "sparse" backfill, like lightrail-esque give me all foo.bar.baz's that have ever existed?

Jim Calabro ♟️
@calabro.io

Yep! You can do something like this from within the jetstream repo, check that ./cmd/client code out. The sample client is a _lot_ of code because it's got "one of everything", so tonight and tomorrow morning I'll be working on some simpler examples

Jim Calabro ♟️
@calabro.io

sweet! the on-disk file format hasn't changed at all, just the lexicons. so, no need to do a full network re-backfill, you can just deploy the server again once you update so, client-facing changes rather than core data model changes