Two tangential "yes and" points: 1) I'm not smart enough to understand differential privacy. So my noob mental model is: Fuzz the data to create hash collisi

Two tangential "yes and" points: 1) I'm not smart enough to understand differential privacy. So my noob mental model is: Fuzz the data to create hash collisions. Differential privacy's heuristics guide the effort. Like how much source data and how much fuzz you need to get X% certainty of "privacy". Meaning the likelihood someone could reverse the hash to recover the source identity. BUT: This is entirely moot if original (now fuzzed) data set can be correlated with another data set. 2) All PII should be encrypted at rest, at the field level. I really wish Wayner's Translucent Databases was more well known. TLDR: Wayner shows clever ways of using salt+hash to protect identity. Just like how properly protected password files should be salt+hash protected. Again, entirely moot if protected data is correlated with another data set. http://wayner.org/node/46 http://wayner.org/node/46 https://www.amazon.com/Translucent-Databases-Peter-Wayner/dp/0967584418 https://www.amazon.com/Translucent-Databases-Peter-Wayner/dp... Bonus point 3) The privacy "fix" is to extend property rights to all personal data. My data is me. I own it. If someone's using my data, for any reason, I want my cut. Pay me.