4 ms·

I really love the design and style qri! It is fun! Can I ask why, for a git-style system, IPFS was chosen instead of GUN or SSB? Certainly, images/files/etc.

I really love the design and style qri! It is fun! Can I ask why, for a git-style system, IPFS was chosen instead of GUN or SSB? Certainly, images/files/etc. are better in IPFS than GUN or SSB. But, you're gonna have a nightmare doing any git-style index/patch/object/etc. operations with it - both GUN & SSB's algorithms are meant to handle this type of stuff. Did you guys do any analysis?

b_fiive 8y ago
hey, qri dev here. Delighted you like the design, we're hoping to make data a little more "approachable" :) We did look into SSB. I'll admit to not hearing about until only a few months ago, but the main reason we chose IPFS was for single-swarm behaviour, allowing for natural deduplication of content (a really nice property for dataset versioning). The majority of our work has been in the exact area you mentioned, building up a dataset document model that will version, branch, and convert to different formats. We've gone so far as to write our own structured data differ (https://github.com/qri-io/deepdiff https://github.com/qri-io/deepdiff). I'm very happy with the progress we've made on this frontier so far. I'm a huge fan of SSB, but don't think it's well suited for making datasets globally discoverable across the network. In the end the libp2p project tipped the scales for us, providing a nice set of primitives to build on.
- marknadal 8y ago
  Nice work!