Would be interested in links to the most personally compelling evidence (in either direction), for those reading.
Search for Craig's blog posts and computer security newsletter groups where he was active 15-20 years ago; he talks about P2P networks, hashing(Craig discusses how SHA-1 is vulnerable and not secure anymore), statistics(Poisson distribution, the same statistical model that was mentioned by Satoshi in the Bitcoin whitepaper).
I found some tids and bits that he and "Satoshi" have in common, plus Satoshi used British English and Craig is an Australian. All of this means nothing but either Satoshi is dead or this Australian guy has something to do with Satoshi and Bitcoin because he wouldn't be pushing so hard as Satoshi persona if he was't involved with Bitcoin in one way or another.
Craig also said couple of years ago that he will share his bank statement of him buy the original bitcoin.org domain but he still didn't do it. Again this would be indirect proof but Satoshi signing his private keys won't be happening anytime soon(and anyone can sign keys if s/he steals them, again indirect proof).
After reading this, it sounds like a great idea to store files using the SHA-1 for the directory.
I have no idea what this means however, all I know is that SHA-1 and MD5 are hashing algorithms. If I calculate the SHA-1 hash using this ruby script, and I change the file's content (which changes the hash), how do I know where the file is stored then?
My question is then, what are the basics of implementing a SHA-1/file-storage system?
If all of the files are changing content all the time, is there a better solution for storing them, or do you just have to keep updating the hash?
I'm just thinking about how to create a generic file storing system like GoogleDocs, Flickr, Youtube, DropBox, etc., something that you could reuse in different environments (such as storing PubMed journal articles or Cramster homework assignments and tests, or just images like on Flickr). I'd probably store them on Amazon EC2. Just some system so I can say "this is how I'll 99% of the time do file storing from now on", so I can stop thinking about building a solid/consistent way to store files and get onto some real problems.
sry for mixing up the two
