←back to thread

663 points nikisweeting | 1 comments | | HN request time: 0.207s | source

We've been pushing really hard over the last 6mo to develop this release. I'd love to hear feedback from people who've worked on big plugin systems in the past, or anyone who's tried our betas!
Show context
orblivion ◴[] No.41863227[source]
Have you (and I wonder the same about archive.org) considered making a Merkle tree of the data that gets archived? Since data (including photos and videos) are getting easier to fake, it may be nice to have a provable record that at least a certain version of the data existed at a certain time. It would be most useful in case of some sort of oppressive regime down the line that wants to edit history. You'd want to publish the tip somewhere that records the time, and a blockchain seems to make the most sense to me but maybe you don't like blockchains.
replies(2): >>41863351 #>>41863987 #
nikisweeting ◴[] No.41863351[source]
Yup, already doing that in the betas. Thats what I'm referring to as the beginnings of a "content addressable store" in the article.

In the closed source fork we currently store a merkle tree summary of each dir in a dotfile containing the sha256 and blake3 hash of all entries / subdirs. When a result is "sealed" the summary is generated, and the final salted hash can be submitted to Solana or ETH or some other network to attest to the time of capture and the content. (That part is coming via a plugin later)

replies(2): >>41863421 #>>41868081 #
1. orblivion ◴[] No.41863421[source]
Wow that's great!