3 ms·
This is completely relevant: http://www.daemonology.net/blog/2012-01-19-playing-chicken-with-cat-jpg.html http://www.daemonology.net/blog/2012-01-19-playing-chi
by SideburnsOfDoom 15y ago
This is completely relevant: http://www.daemonology.net/blog/2012-01-19-playing-chicken-with-cat-jpg.html http://www.daemonology.net/blog/2012-01-19-playing-chicken-w... ("Playing chicken with cat.jpg" by Colin Percival from tarsnap)
> "The answer isn't for ... the company ... to prove that they can be trusted; the answer is to ensure that their customers don't need to trust them. ... The best way to avoid privacy breaches is not to formulate a detailed privacy policy; it's to reduce your capabilities so that you're unable to violate anyone's privacy."
Just think of what target companies like this will make for hackers. It's an accident waiting to happen.
- sunchild 15y agoTrue, but in some cases, data integrity concerns outweigh the desire for total obfuscation.
- joe42 15y ago>It's an accident waiting to happen. It'll be a shitstorm when a large set of address books gets leaked to the internet (à la AnonOps, etc.). (Though it would be a lot of fun to run some graph-theoretic metrics on the dataset (closeness, centrality, etc.). I've often lusted over getting an anonymized version of the Facebook graph (32-bit ID for each person, assume average of 100 friends, 700 million users, gives a total size of about 300 GB uncompressed), but a leak of a couple million address books now seems not far-fetched.)