Hacker News new | past | comments | ask | show | jobs | submit login

Of course you have a choice, but in reality who leaves a site because they see that warning? I imagine almost no one. Hell, I understand the implications and I don't care because site X has what I'm after and perhaps no one else does (or they all have the same warning anyway.) I have no reasonable option but to accept whatever these sites want.

The warnings accomplish nothing. It's just another nag screen. It was a bad idea when it was thought up and it still is today. It's an attempt to seal a wound (misuse of personal data) with a piece of string. It wasn't even a half decent band-aid.






... and users appear to disagree on whether there's a wound to seal.

It's difficult for the average person to understand the long term implications of this sort of data collection. They don't realize how powerful all these little details can be when put together.

And there's another category of people that understand but don't care.

Not proud of it, but I fit somewhere in that bucket. I do consider it and I have made (slightly) inconventient choices in the name of privacy, but when it comes down to it, I typically say "screw it" because I want what I want.

Oh yeah, I'm definitely including myself in that bucket too.

The warnings under the old law were idiotic. Under the GDPR, however, you're required to have clear consent with an easy refusal option. But just like the cookie warning, so, so many sites are violating that requirement because, hey, you cannot go after everybody, right? I don't think there were really any consequences for violating the old cookie law, so the majority are maybe approaching the GDPR the same way (even though this time there are actual punishment options.)



Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: