Log in | Sign up

I had the exact same reaction.

If the biometric ID is collected and stored by someone else, not only have I lost my anonymity, I’ve also lost control of my identity and there’s no way for me to stop that happening.

This is unequivocally bad for privacy.

Exactly!

Biounique id is an advertiser’s wet dream and I don’t think it’s theoretically possible to prevent it from being exploited for profiling by Google. If the hashed encrypted token retains the uniqueness then it points to you as an individual across time, devices and location changes. There is no escaping this ID. You can’t change it, you can’t get a new one.

Google and other multinational corporations WILL know where you live and can figure out all your personal characteristics with a little time. Your anonymity is gone forever.

Sam Altman saw the film Minority Report in which iris scanners on holographic billboards trigger the advertisements to address you by name, hampering the escape of the central character who was being set up, and thought “Cool, let’s make this. I’m going to be rich! The other dystopian aspects of the film are fiction, but this one I can make real.”

Scan your biounique eyeball to provide ID whilst retaining your anonymity???

Anonymity and the ability for someone else to prove it was me are nearly opposites.

Brit here. I had no idea about the rock formations under the Irish sea. None whatsoever. I don’t think it’s on the GCSE geography syllabus!

Estimating by the next reply you got, maybe they’re being sarcastic on a long timescale.

The CO2 problem is a pretty big problem to solve, to be fair. I charge my EV at night when the ejection is really cheap because it’s nearly all wind power.

Well, they solve the pollution problem in built-up areas and they solve the CO2 problem if you increase solar and wind power. The one thing they don’t solve is the congestion problem.

I always thought that NaN is required by IEEE rules to never equal any other number, including itself, because you can make NaN in different ways and this shouldn’t result in equality or something, so C is wild but not javascript’s fault.

The other three being true is definitely javascript’s insane fault, though.