When done properly is going a lot of heavy lifting there. Time and time again it's been found most aggregates are not filtered properly and be deanonymized with eaze.
It's not that one is big bad, and one is little bad, it's the little bad can become big bad with a small amount of work by an attacker/company. Then when you add in zero external third party verification of these company claims, you really don't have any reason to believe them.
> When done properly is going a lot of heavy lifting there.
Not really. There are common practices for it. Yes it hits HN when deanonymization can happen at a well-known company, just like it hits HN when there's a security vulnerability that gets patched at a well-known company.
But "it's the little bad can become big bad" is what's doing the heavy lifting in your argument. No, that's not how it works. There's no universe in which aggregate data can be deanonymized to anywhere close to what all of the individual profiles would be. It's a completely false equivalenace, period.
When done properly is going a lot of heavy lifting there. Time and time again it's been found most aggregates are not filtered properly and be deanonymized with eaze.
It's not that one is big bad, and one is little bad, it's the little bad can become big bad with a small amount of work by an attacker/company. Then when you add in zero external third party verification of these company claims, you really don't have any reason to believe them.