4 ms·
Most of us in Europe don't find it especially vague, poorly written or overly broad. I think most of us are firmly in favour of it, and not especially concerned
by oldcynic 8y ago
Most of us in Europe don't find it especially vague, poorly written or overly broad. I think most of us are firmly in favour of it, and not especially concerned by the effect on our companies, especially when we've already been doing some of this under current data protection.
Personally I think it's an excellent attempt to bring some sanity back to our online privacy. It's perfectly readable and understandable by an individual. Though of course it's not perfect. What is?
It's been fascinating and extremely educational to see in the numerous HN discussions how many from the US are managing to view it from entirely the opposite point of view.
- zerostar07 8y agoWrt to vagueness i have to respectfully disagree. Perhaps an opinion poll would help, but from what i 've gathered from Q&A forums that are frequented by europeans in the past weeks, it's freaking vaguety vague. to the point where it's not clear how broad it is at times. Maybe it reads fine if you are a "data subject" (i hate this term btw) , but if you actually need to comply its hard, even for the simple stuff that every website has. E.g. cookies, advertising, backups I 'm not even sure if the data subject can figure out what to expect from GDPR. E.g. Is HN compliant? Can you tell if a website you visited today is compliant?
- ryanwaggoner 8y agoMost of us in Europe don't find it especially vague, poorly written or overly broad. Yes, you all keep saying that, often while tripping over each other with contradictory explanations of when it applies and how to interpret it. Yes, truly well-written and not vague at all.