I think this is the relevant part of this whole samsung/toshiba SSD thing;
Does it matter in real life? It would seem like the answer is “no”.
Dutch journalist dude just now
In case you’re wondering how y’all’s shenanigans are being explained in other countries.
That’s how a lot of us view it too. I’m doing my best to screw my eyes shut, cover my ears, and shout LALALALALALALLA so I don’t go into Terminal Panic Mode.
^^^^That. Because honestly? There’s not a lot we can do. The people blocking any efforts at compromise do not give a fuck what we think, and all the letters/emails/faxes in the world aren’t going to change that.
Both sides have this wrong.
To those on the right, this is not the time to do this. If you didn’t like how the money was being spent, the time to make your voice heard was in the budget process. When you passed the budget, you knew that the US was going to have to raise the debt limit. If all of a sudden you got religion and want to change the budget after the fact, you’ll have your chance in a couple of months.
To those on the left, why aren’t you calling the right out on this? Why are you letting them pretend that “debt limit” time is the right time to change the budget and playing along with them ?
I really like this quote. The more I read it, the more I wish I had heard it, or something very like it, back in 2001.
From what I understand, in the name of de-duplication (if multiple users upload the same file, only one copy will be kept), Dropbox will store only one copy of any 4MB chunk that has the same SHA256 hash.
This is a recipe for disaster. Mathematically, once you hit 32 characters, you start running the risk of hash collisions (two DIFFERENT files with the same hash). The math is = there are 256^32 possible files containing 32 bytes of binary data (encrypted, binary data, etc), which happens to be the number of unique hashes that SHA256 can produce = 2^256 (try it - they are the same 78 digit number).
So, once you hit length 33, you are guaranteed that there will be a potential collision with another file with the same length (not to mention collisions with files of a different length) — and Dropbox will only store one of your files. This means that either “Dropbox kept your version of the file and when the other person downloads the file, they will see your file” or “Dropbox kept their file and you get to see the other person’s file (but your file - or piece of your file - is lost forever)”. I don’t like either scenario.
Now, this is just mathematics at this point. Whether you will see this actually happen in Dropbox depends on how lucky you are. At the 33-byte level, it is very unlikely that two files will have the same hash, BUT MATHEMATICALLY POSSIBLE. However, at the 4MB chunk level (iso files, videos, lossless MP3s, etc), for any given 4MB chunk, there are 131,071 other chunks with the exact same hash. Boggles the mind.
So, you’ve got to ask yourself one question - do you feel lucky? The more files you upload, and the larger the files are, the larger the odds against you. Eventually, you will lose files. Some of the other topics in the Dropbox forums that talk about data loss may already be victims.