[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: expand tombstone explanation
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: expand tombstone explanation |
Date: |
Mon, 26 Apr 2021 23:13:57 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 68e2450 expand tombstone explanation
68e2450 is described below
commit 68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Apr 26 23:13:52 2021 +0200
expand tombstone explanation
---
design-documents/019-wallet-backup-merge.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/design-documents/019-wallet-backup-merge.rst
b/design-documents/019-wallet-backup-merge.rst
index ceedfb3..3c4541f 100644
--- a/design-documents/019-wallet-backup-merge.rst
+++ b/design-documents/019-wallet-backup-merge.rst
@@ -131,7 +131,9 @@ Q / A
* A: When syncing with a backup server that still has an old version
(but same device ID and wallet root pub), the tombstones ensure
that no old data is re-surfaced that has been deleted in later
- versions.
+ versions. This can happen in practice even with only one device,
+ namely when a backup provider is unavailable for a long time,
+ but then becomes available again.
* Q: Why are tombstones only GCed after exceeding an age threshold?
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: expand tombstone explanation,
gnunet <=