#dat

pfrazee: if you've got a repro that'd come in very handy

pfrazee: these are exactly the kind of messages I never hope to see haha 😅

pfrazee: I'm not aware of any issues with it at the moment, but if something is failing I'd be happy to dig in and fix it

yoshuawuyts: hah ok, I'll get around to that in a bit

mafintosh: woot my gist works w/ new hyperdb

ogd: awesome!

ogd: so now you can impl npm on top

I found a nice way to load binary assets cross-platform different than the browserify readFileSync polyfill

I tend to write for browsers first and then polyfill node to match them. I find that direction works better and keeps my browser code clean and short where bandwidth really matters.

(this particular example is using mafintosh's blake2b wasm code :D)

(fwip) Quick question: When sharing datasets, it looks to me like dat first copies the dataset into a dat-managed zone, effectively storing the data on-disk twice. Is there a way to say "Please share this 250GB directory" without requiring an additional 250GB of storage on-hand?

jhand: ^

@fwip to share data, dat indexes the files - it doesn't copy them anywhere. So you should still be able to share that folder without much extra space (just enough for the metadata, which is small)

(fwip) Oh, that's sweet. Thanks for answering!

mafintosh: can i close a hyperdb? or do i just close the underlying hypercore. trying to write some tests