That add-on works great. On firefox. On a desktop. Of a computer I own. That's not exactly covering a significant portion of my use cases.
Also: I really don't care about analytics cookies, I think they are fair game and can genuinely make many websites/tools better when used correctly. So how can I express this measured and informed consent globally ? (Answer is: I cannot due to how the law is written). And with ton of added legislation, the user life won't get any easier.
I don't understand the parallel with chlorofluorocarbons. Banning that substance stopped its production and thus its harmful effects. PII on the other hand are - as you mentioned - defined so broadly that they are everywhere. Simply having a login button means you deal with PII. Having access to the user IP (aka: replying to an HTTP query !!) means dealing with PII. Sending an order confirmation by email means dealing with PII. You can legalise all you want, but these data are still going to be there: their production will not stop the slightest. In almost all the cases their usage does not cause any problem, unlike chlorofluorocarbons.
> That add-on works great. On firefox. On a desktop. Of a computer I own. That's not exactly covering a significant portion of my use cases.
That is why you should be happy about GDPR as it covers all your use-cases.
GDPR is actually great but no one reads it and only listens some scaremongering by companies that are hurt by it. The problem of mass surveillance and abuse of personal data is also huge. But again no one thinks about it outside some cookies and ads.
Enjoy watching about GDPR: https://www.youtube.com/watch?v=-stjktAu-7k (best done presentation that I was able to find on internet, you might notice in first few minutes that is not about you having access to PII but about using PII - or: I have access to a gun. But I wont use or abuse it. As I might end in jail.)
Also: I really don't care about analytics cookies, I think they are fair game and can genuinely make many websites/tools better when used correctly. So how can I express this measured and informed consent globally ? (Answer is: I cannot due to how the law is written). And with ton of added legislation, the user life won't get any easier.
I don't understand the parallel with chlorofluorocarbons. Banning that substance stopped its production and thus its harmful effects. PII on the other hand are - as you mentioned - defined so broadly that they are everywhere. Simply having a login button means you deal with PII. Having access to the user IP (aka: replying to an HTTP query !!) means dealing with PII. Sending an order confirmation by email means dealing with PII. You can legalise all you want, but these data are still going to be there: their production will not stop the slightest. In almost all the cases their usage does not cause any problem, unlike chlorofluorocarbons.