microcosm.blue
Streaming Tree ARchive format
what it's not
bad-example.com
+4
-1
readme.md
+4
-1
readme.md
···
50
51
- It should work for "CAR slices" -- contiguous narrowed partial trees that may omit content before and/or after a specific key. (CIDS referencing missing nodes at the boundaries cannot be eliminated)
52
53
-
- It's desireable to be able to archive complete *subtrees*, so enforcing a well-formed atproto commit as the header might not be sufficient on its own. (subtrees could be stored as CAR slices so this may be unnecessary)
54
···
50
51
- It should work for "CAR slices" -- contiguous narrowed partial trees that may omit content before and/or after a specific key. (CIDS referencing missing nodes at the boundaries cannot be eliminated)
52
53
+
- It's desireable to be able to archive complete *subtrees*, so enforcing a well-formed atproto commit as the header might not be sufficient on its own. (subtrees could be stored as CAR slices so this may be unnecessary)
54
+
55
+
- It *might* be interesting to allow arbitrary sparse trees. Not sure yet.
56
57
+
- It's not suitable for firehose commit CARs, which need to include blocks that aren't in a strict single MST.