Nested block support to keep data available #13

Open
opened 2020-10-09 07:22:13 +00:00 by kev · 0 comments
kev commented 2020-10-09 07:22:13 +00:00 (Migrated from git.voidnet.tech)

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

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
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kev/Onionr#13
No description provided.