this post was submitted on 09 Sep 2023
604 points (96.7% liked)
Programmer Humor
31340 readers
1272 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It makes no sense at all to distribute the backup generation step, and what do you do with your ledger once the retention period ends?
There may be something you can do with a ledger in the "full - incremental - incremental - incremental ..." cycle, but I can't think of anything that's actually useful.
Since we are designing the consensus algorithm we could remove data that is expired with some quorum vote, or indication from a key holder.
or you could just not do that, and keep control of your own data. Why the hell would I want you to have a vote on whether I can delete my private data, which for some unfathomable reason, someone decided everyone should have a copy of?
In practice, data owners don't have control of their data, sysadmins do. This gets complicated in multi-orgnizational data setups.
the sysadmin is part of the owner
data owner was the key one here. If I run a storage service for example, I have control of the data, but you would see it as a breech of trust if I deleted your data, or gave access to someone else without your permission, because you in the scenario are the data owner.