Nested block support to keep data available #13
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kev/Onionr#13
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It should be possible to reinsert blocks by making a new block denoted by a special meta tag. Older copies would be automatically erased. The previous hash(es) could be in truncated form.
Clients could remember and associate old hashes to new ones, this would preseve file shares or other data.
Blocks should only be nested one level to avoid exponential growth