@yoshuawuyts as promised, deets on what precisely is my issue with keys in dat:https://gist.github.com/tmcw/cfb7ac4fda5f00905b656fa7830a7b87 …
-
Really liking it so far. Commenting as I'm reading through it: Dat has two (2) sync modes: 1. Store all data as separate files on disk. Intended for personal computers. 2. Store data as a big blob on disk. Intended for servers. So depending on the scenario, .dat dir is enough
Finished reading it. Nicely written; thanks for being so elaborate! Being a solutionist it seems that for any dat to be resilient, it must at least have: - one full backup of the archive on an external location, always syncing - one backup of the keys, stored securely 1/2
-
-
You're right that ensuring that peers are synced is a tricky problem. If you have more data than a peer, you can check if it's up to date. If you have less data then the peer, you can't. Believe there's methods to check peer status tho! We should probs expose them better somehow
-
Peer %s aren't exposed anywhere in the default dat CLI as far as I can tell. UX-wise, I think it's awkward that a dot-directory that users will probably treat as an implementation detail is essential to ownership over a thing, on some systems the finder won't even show it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.