Re:Cleveland.com’s ‘right to be forgotten’ removes names fro...
by cribbles on Friday October 19, 2018 @03:20PM
(#18259223)
Why not just provide a hash for each version of the document?
[ Parent
| on HN ]
Re:Cleveland.com’s ‘right to be forgotten’ removes names fro...
by RileyJames on Friday October 19, 2018 @06:58PM
(#18260693)
That’s exactly how this kind of this is done, using a blockchain. Here is an example of using Tierion (blockchain) to stores hashes of accounting documents, in order to create a probable audit log. https://medium.com/tierion/xero-integrates-with-tierion-to-s...
It seems like the same concept would apply to storing hashes of any other document, such as a newspaper article.
Re:Cleveland.com’s ‘right to be forgotten’ removes names fro...
by reubenmorais on Friday October 19, 2018 @03:50PM
(#18259480)
That's essentially what a blockchain is, except you also include the previous hash in the version you're hashing, so that changing one record invalidates all future hashes.
Re:Cleveland.com’s ‘right to be forgotten’ removes names fro...
by rwcarlsen on Friday October 19, 2018 @03:50PM
(#18259478)
But that just changes the problem to one of archiving the hashes immutably.
Re:Cleveland.com’s ‘right to be forgotten’ removes names fro...
by fuzzybeard on Friday October 19, 2018 @04:23PM
(#18259744)
Which is what blockchain does. We're experimenting with using it to create audit logs of data, which can't be tampered with.