Post

STAR-lite for atproto space archives, tentative format pitch (and... is it time to just call it STAR?)

tangled.orgstar-lite/spaces-archive.md at main · microcosm.blue/starSTreaming ARchives: stricter, verifiable, deterministic, highly compressible alternatives to CAR files for atproto repositories.

fig (aka:[phil])

@bad-example.com

@dholms.at @bnewbold.net WIP pass at generic meta (and more generic over all with spaces as an application): tangled.org/microcosm.bl...

tangled.orgstar-lite/spaces-archive.md at star-lite-v1-generic · microcosm.blue/starSTreaming ARchives: stricter, verifiable, deterministic, highly compressible alternatives to CAR files for atproto repositories.

daniel holmgren 🫠

@dholms.at

nice this looks like basically exactly what i had in mind one last question: are `val` in the data section always dag-cbor (and can therefore be decoded while deserializing the STAR)? or is it arbitrary bytes (in each case a second pass is requierd per-value)?

daniel holmgren 🫠

@dholms.at

maybe STAR could specify it as "bytes" and then particular use cases (like for repo data for instance) could require DRISL

fig (aka:[phil])

@bad-example.com

yeah was thinking unspecified bytes for star vals and the application restricts further if they want. i think this is still easy-ish to do zero-copy with a generic streaming archive reader. not opposed to drisl-only vals or other restrictions in v1 if it’s an easier path for spaces though!

25/9/26, 8:43 pm0 reposts2 likes

No replies yet.