Joe Hand

Yes... but perhaps not optimal (or well documented). As you say, I did this so large dats can start importing while counting is still happening, since that can take awhile....

> Perhaps it could be useful to implement some sort of approximation indicator for while the initial count is still being calculated Yea, this is how I started the implementation...

This is also true of a clone, for example with https://github.com/joehand/dat-clone-sparse-test. If the `.datdownload` file exists we should always selective sync. May be better to implement this in dat-node.

> will it be possible to pause download and still share data for upload ? Ah, good point! The method I wrote above, using `archive.unprioritize()`, will work with stopping downloads...

Implemented a first version which is a proxy for `join` and `leave`. I had some trouble with unreplicate or unprioritize because of hyperdrive/swarm API issues. I will revisit pause/resume when...

Mafintosh said this is something he wants in hyperdrive, so I'll probably leave it as an alias for join/leave until implemented in hd.

To download `dat.json` before knowing the directory we'd have to put the database either in a temp directory or use a memdb to download the file before making the real...

@joehand you didn't think this through 6 days ago before you commented. You can create the directory using the key and once the clone is finished, rename it to whatever...

Ideally, we'd implement (part) of this in dat-node. It goes along with: https://github.com/datproject/dat-node/issues/30 Be nice to read the dat.json whenever it appears in metadata and add that info to the...

Save clone dir to a tmp folder until it done then rename to `name` if in dat.json or `key`. * What happens on partial clones? Its still nice to be...