I recommend watching the film "Democracy"[1], which showed how an EU data protection law went through the process to become law. The "main character" (chair of the process) was a German MEP. The thing I best remember him saying[2] was in response to some lobbyists, who wanted to know why he was pushing back against their business interests when they were all united. The MEP said he primarily represented the thousands of people in his constituency, even though they couldn't afford to send lobbyists to Brussels.
With some stronger wording ("This site shares your data, including the web pages you view and where you click, with the following companies: Google, AdNetwork234, ..., These companies use it to sell advertising to you and may further share your data") the cookie law could have been stronger.
The MEP was in the Green party, but most aren't -- pressure from individuals on other MEPs would encourage other, more business-friendly MEPs, to push back against the lobbyists.
[1] https://www.theguardian.com/technology/2015/nov/14/democracy...
[2] I think it was in the film, but I also went to a screening with him giving a talk afterwards.
The only thing legislation like that does is make companies pay people like me a little more to implement popups that annoy their users.
If, instead, it said "Every click you make on this site is recorded and sent to four unrelated companies" the public might just have taken a bit more notice.
There are signs all over California telling you that the appliance you are going to buy might kill you and nobody cares. You think they are going to care that some unrelated company will find out what you are reading on Medium?
However, these banners have also clearly caused millions of people to ask the question "What's a cookie" which leads some of them to start caring about this issue.
We definitely got the nag screens¹, but improvement?
[1] Which is totally inferior solution technically & ux-wise, because the user/client voluntarily accepts the cookie from the server, and there's already setting for that in the browser.
But everyone construed that cookies <=> nag, because nobody RTFM.
The legislation called for informed consent. Two core issues were left open to definition, in practice. [1] What requires informed consent? [2] What counts as informed consent.
For question 2, a standard answer (nag screen) emerged.
Question 1 is trickier. The cheapest & easiest solution is to just nag, so that’s the default. If you want to drop the nag screen you can deal with question 1, but most don’t bother. Either they want the tracking, they want the easiest option or they want legal CYA.
I think the legislative intentions were good, but this was a hard area to legislate. It didn’t work, IMO.
There's only so much a browser can do against someone who can follow your IP address around. What we really need is ISPs who randomize what the server sees from their pool of IPs and NAT it internally.
It's ISPs that worry me the most. They see all the places you connect to. Even if you use https, they still know the endpoints.
I know a lot of people have hopes for a legislative solutions, but I think the EU (also UK and others) "cookie law" really needs to make us consider how effective they can be. The motivation for the law was good. They put their finger in the right place. . We got nag screens and little improvment in privacy.
Not every piece of privacy legislation does as little as this, but I still think we need to be wary. Browsers, OTOH, are in a great position to improve user privacy.
Maybe instead of letters to parliamentarians, letters to browser makers?