An exception exists where the cookie is "strictly necessary" for the provision of a service "explicitly requested" by the user
Strange how all those lawyers aiding the writing of the law would miss such a thing ...!?!
That is very very risky. Let's say that [popular-site-with-logins] is hosted in EU and switches to ?sessionid=... style. Now people start sharing links to their content in the "normal" way (select url, copy, paste) and suddenly you have problems with random users being logged in as someone else. (or you have to limit session to ip, which annoys mobile users)
A steering wheel in a car is not strictly necessary to drive it. Drivers could physically turn the tires.
And so on.
Strange how all those lawyers aiding the writing of the law would miss such a thing ...!?!
Strange how all those lawyers aiding the writing of the law would miss such a thing ...!?!
Sure, other (non-sign-up) functionality might also need cookies (changing font size, switching themes, the small things) and you might not want to annoy the user with stupid checkboxes for those kinds of stuff, but other than that?
I still don’t see the big scandal.
Now comes the hacks: serve javascript with a unique id in it. Set the cache policy to never re-download, or recheck the file. Use you lawful (semi) permanent cookie.
The user obviously asked for the data to be stored, since it's part of caching.
Or am I going to have to ask the user before being allowed to cache anything locally?
Stil think it's a nonsense law though ..