Confusion Surrounds UK Cookie Guidelines
pbahra writes "The Information Commissioner's Office has, with just over two weeks to go, given its interpretation on what websites must do to comply with new EU regulations concerning the use of cookies. The law, which will come into force on 26 May 2011, comes from an amendment to the EU's Privacy and Electronic Communications Directive. It requires UK businesses and organizations running websites in the UK to get informed consent from visitors to their websites in order to store and retrieve information on users' computers. The most controversial area, third-party cookies, remains problematic. If a website owner allows another party to set cookies via their site (and it is a very common practice for internet advertisers) then the waters are still muddy. And embarrassingly for the Commission — it's current site would not be compliant with its new guidelines as it simply states what they do and does not seek users' consent."
...a law stopping people from making laws about things they simply do not understand.
Correct way to handle cookies:
http://www.youtube.com/watch?v=OqL7jyrXhLs
http://www.youtube.com/watch?v=rHfEmIXkWfg
http://www.youtube.com/watch?v=Cqz9ZXUoUcE
These posts express my own personal views, not those of my employer
IANAL(imey), so I'm having trouble understanding why the UK law bans the use of biscuits. /girds loins/
Failure to follow this advice may result in non-deterministic behavior.
It's just next to impossible to use the law as it is.
To me however it is very simple: A website can trivially obtain permission from the user for the site's own cookies. An advertiser needs to get opt-in consent before sending a cookie as it is unfeasible to obtain permission as you go. Basically this can be done in a simple way: A visitor to a site featuring ads from the advertiser will see nothing to requests to decide whether to accept cookies or not until this decision is made. The result is stored in a cookie which they need permission for as well. Now when sending ads the decision cookie is checked and if the answer is yes, the ads are sent with the tracking cookies, and if no, they are sent with no cookies.
This will obviously result in a lot of people saying no to the tracking cookies but that is as it should be. Tracking someone should only be done with consent.
"For every complex problem, there is a solution that is simple, neat, and wrong." -- H.L. Mencken (1880-1956) --
Not True.
Yes we have biscuits, but we also have cookies. Cookies are typically rough circular baked sweet dough with added fruit or chocolate. Most Cookies are also moist in the centre. They are also baked fresh and bought from dedicated cookie or bakers shops (you can get pre-packed cookies but these are horrible and dry).
Biscuits are dry (excluding the filling) and come in defined shapes. To use a common example, Oreos (also available in the UK) qualify as biscuits not cookies.
-Jar
Together, We Can Make Slashdot Better. I Do NOT Mod ACs. - Check Me Out
There shouldn't be any client side storage at all. If the browser makers would just drop this stupid cookie idea that Netscape had around the time of the blink-tag, web developers would be forced to design their sites to store anything they need on the server.
Make the browser send a UUID as a session identifier. When the user types in a new URL, or selects a bookmark, generate a new session identifier, even if it's the same site. That way, you could even be logged in to the same site with two different userids at the same time, something that doesn't work with cookies. When the user navigates from one domain to another, generate a new session id. When loading images or scripts from a different domain than the current page, load them with a new session id.
No tracking possible.
"Remember me" would no longer be a setting on the page, which writes a permanent cookie, but a setting in the browser, which makes the current session id fixed for the current domain.
Remember the CAN-SPAM ACT 2003 in the US? That was another pointless law. Spam is at an all time high. You only stop spam with a spam filter. Governments only gets bigger, never smaller.
From the guidelines (pdf):
So, by my reading of that, you do not need further consent merely for logins/session cookies:
The definition of a computer file, from wiktionary: "An aggregation of data on a storage device, identified by a name."
That definition was what I was taught when I studied CS in the 80's too, it goes back to the 60's.
That definition clashes with the Unix philosophy of "Everything is a file" which allows us to abstract from different peripheral devices and treat them all uniformly.
Is /dev/disk0 a file? I'd say no, because it is the storage device, not just the data on it. (E.g. you can use it to query the SMART status of the storage device which I would not count as the data stored on it.)
Is /dev/kmem a file? It's data, but it's not on storage, but in volatile memory.
Most files below /proc are not even data at all, but state. (I.e. their informational value depends on the time they are queried.)
Also, a database file is usually not a text-file, because it contains data that is not human-readable.
Free Manning, jail Obama.