today I created a burner google account. these days google requires an Android phone in order to even create an account so I used an old phone to scan the QR code ( I am pretty sure this lets google grab all of the metadata of the mobile phone ). after about 1 hour creating the account. google’s automated system disabled the account however I appealed and got the account back. before someone asks I need google because of where I live.
this made me wonder what if google mandates age verification? if there were age verification google would immediately notice that I am creating another account ( burner account ) which it won’t like. burner account won’t be created in the first place!
we already have too much surveillance and this makes it worse. my mobile number is already tied to my read government identity. I DO NOT want my online account to be tied to my read identify too! it is sad, it really is
You’re talking about potential implementations. EFF is talking about issues in current implementation. As I said in my very first comment, I’m sure it can be done properly. The EFF is worried that if the current implementation is rolled out now, the system will stay unfixed for years and make privacy even worse.
But anyways, since you seem knowledgeable about the EUDI implementation and I’m too lazy to look it up, do you know if the current implementation allows a website to collude with the issuer to get the identity of a user?
My reference point is cloudflare’s research on zero knowledge proofs used to issue anonymous tokens to bypass (pre-complete) captcha checkpoints.
Neither website nor issuer (nor the combination) can determine the identity of a user from the token (hence zero knowledge), but other techniques entirely unrelated to the cryptography can identify a user. For example network or browser metadata or traditional browser fingerprinting.
I see so it seems like we were talking past each other. I’m aware of Cloudflare’s token system. As well as other systems like GNU Taler and Monero. So clearly privacy preserving systems can be built. But I also trust the EFF, and if they say the current system has major flaws I’m inclined to believe them
The age verification system can’t be zero knowledge if they know what your token is, and can track it. Seems a bit funky
As you said, there’s still metadata. For example, if they requested a new token every time you used one. Technically the token itself is still zero knowledge, but now the issuer knows when you use it.