Martin Heidegger

> can’t do this on 50m directories ahead of time That is not what we are suggesting here. In pfrazee's approach you'd only serve a DAT once you have it...

> i.e. if a change happens after a file is added then presumably the same mechanism (and I don't know how DAT does this) to handle an update would be...

@mitra it is stack-able. You could a root-set of 512 keys, each containing 512 more, each with 512 in them, which would mean 3 more look-ups for getting to the...

Things I miss specified: - `Version`: What is considered a version in DAT? - `Bootstrapping`: What do we mean when bootstrapping the network? - `Sparse`: DAT's can be "sparsely" replicated?!...

@aral I am considering working on an "encrypted DAT". :DATs that are additionally encrypted with yet another key in order to implement proxies/bridges that don't know about the content of...

Thanks, naming is hard :-)

What entails "sync" in `dat sync` and "share" in `dat share`? (Question that came up in chat) Also: how to call a peer that has a write key vs a...

"authorised" makes sense in a multiwriter context, but in a single-writer context (that will exist in future) it feels weird as there is no way how to every authorise another...

@RangerMauve "pinning service" was also known as "publishing": https://github.com/datproject/dat/blob/master/src/commands/publish.js - `registry`: A server that can replicate a DAT - usually with a login - `publish`: Telling a registry to replicate...

@RangerMauve Do you think registry/publish is worse than "pinning service"/pinning? (is it the same thing?)