News for hackers. Stuff that matters.
Re:Addressing Recent Claims of “Manipulated” Blog Posts in t... by simias on Wednesday April 25, 2018 @10:34AM (#16921835)
I was thinking about using an existing blockchain such as Bitcoin. Of course then the inconvenient is that archive.org would have to pay a fee every time they submit a new hash. A comment above pointed out that the scheme I described (unsurprisingly) already exists at https://petertodd.org/2016/opentimestamps-announcement

Realistically it might be overkill though, simply setting up some mailing list where anybody can subscribe and be sent the checksum every day or even just publishing it at some URL and letting users scrap it if they want might be sufficient. If we're talking about one checksum every day it's only a few kilobytes every year, it shouldn't be too difficult to convince a few hundred people and organizations around the world to mirror it.

Re:Addressing Recent Claims of “Manipulated” Blog Posts in t... by dumbfounder on Wednesday April 25, 2018 @12:44PM (#16923354)
I think you need a checksum for every page, not every day. How would you independently verify the checksum for an entire day?
Re:Addressing Recent Claims of “Manipulated” Blog Posts in t... by rocqua on Wednesday April 25, 2018 @05:16PM (#16926248)
Merkle trees. Whomever wants to store a timestamp for some message stores the path from that message to the root of the Merkle tree. Only the root of the merkle tree of each day needs to be published.