Post

some notes parallel to @dholms.at: I'm confused why the commitment (integrity?) hash would not go in the header CBOR. I like having magic! and it being extensible. combining the "type" and "version" together in a single byte might work?

as danny notes being able to do a "multi-space" repo account export might be nice for backup+migration. though maybe that could just be a zip or tarball. ability to do a single space record would be nice, wrapping a CBOR record. maybe a different magic version and header CBOR '$type'?

I've always kind of wanted a way to optionally include blobs. maybe that could be a second section, after all the records, with path 'blob/<cid>'? varints: i'd stick to what is currently used count in header: I'd probably skip? feels like Content-Length HTTP header would be more useful (but hard)

No replies yet.