mirror of https://github.com/perkeep/perkeep.git
51e88cac65
A planned permanode involves setting the contents of the permanode (instead of a random string) as well as the OpenPGP signing time so the resultant bytes of the blob (and thus its blobref) is deterministic. This allows multiple independent devices (my laptops) to create the same permanodes for the same files (photos backed up from my phone) when offline (airplane) and then when they sync later, still only have one permanode per unique file. This means that tagging and other metadata applied to permanodes on one laptop merge cleanly with metadata from the other. |
||
|---|---|---|
| .. | ||
| go.crypto | ||
| goauth2 | ||
| leveldb-go | ||
| rsc/fuse | ||
| snappy-go | ||