bnewbold

Hey @yoshuawuyts, check out https://github.com/datproject/docs/issues/93 This will presumably get documented in to a SLEEP DEP eventually (https://github.com/datprotocol/DEPs, to replace/update the old whitepaper), but I don't believe anybody is working on...

You might also find these other documentation-related issues helpful if you're doing an implementation working off the whitepaper, particularly if you want to support current (pre-hyperdb) hyperdrive: - https://github.com/datproject/discussions/issues/77 -...

As far as I can tell, deletions are handled by writing a new `Node` at the old path with no `Stat`. `children` for this `Node` should have all references to...

There is another level of complexity: deleted nodes (aka, empty nodes or "tombstones") can be be garbage collected on any write to the register. This is tricky/hard! Will probably be...

I'd still love to see this! Or at least flags to `dat init` (CLI) which ensures all future added/synced data is saved, and a flag to `dat clone` that both...

Hi @kousu, thanks for raising this concern! I don't understand the first paragraph of your second comment, could you rephrase it? ("what to send based on", "every update"). Also, could...

What about `metadata.latest` and `metadata.ogd`?

Secret keys end up in `~/.dat/secret_keys//`, where discovery key is in hex; the first two hex characters are the shard, and the rest of the key is the file name...

I did some reverse engineering, and now speculate that: - the children sub-arrays for a given entry includes entries for all files and subdirectories for every parent directory of the...

In the current protocol, `endsWithSeq` is always set for additions, and never set for deletions.