Replies: 2 comments 3 replies
-
I would like to hear more about the original use case(s) that prompted this discussion @matthme @zippy Overall I see 3 potentially good features:
|
Beta Was this translation helpful? Give feedback.
-
i like the notion of dehydrating cells.. and auto-disable archive options |
Beta Was this translation helpful? Give feedback.
-
Background
Clone cells can be created, enabled and disabled, as well deleted. When a clone cell is deleted, all of its data is erased and cannot be restored. Further it cannot be re-created identically, because it would lead to a source chain fork from the peers' perspective. The data is not guaranteed to be available in its entirety and private entries are never stored on the DHT, so the previous state of a cell cannot be reestablished once it's been deleted.
Every active cell causes network traffic and possibly increasing disk usage. Therefore clone cells can be disabled to prevent these effects from happening.
Suggestion
On top of that we can extend the delete feature to provide an additional stage of deletion. Usually public entries will take up the most space of a source chain. The intermediate step would be to only delete those public entries and retain the private ones. In theory that would also make re-creation of the same clone cell possible.
In a final deletion step, private entries of the clone cell would be deleted too.
Beta Was this translation helpful? Give feedback.
All reactions