BBC Site Uses Cookies To Inform Visitors of Anti-Cookie Law
Andy Smith writes "As of 26 May 2011 web sites in the UK must get a user's permission to set cookies. If you go to the BBC's commercial TV listings site Radio Times you'll see a message telling you about the new law. Go to the site again, though, and you don't see the message. How does the site know you've already seen it? By setting a cookie of course! It doesn't ask for permission."
I guess that's what happens when law makers don't really get what's going on, and the techies tasked to implement this stuff don't really care.
Waiting for an amusing sig.
shows how stupid the cookie law is
Not all cookies are tracking cookies; legislators appear to have overlooked this.
The new cookie laws are only about tracking cookies, not session cookies or cookies necessary for the functioning of the website.
That cookie is not a tracking cookie, as such it isn't breaking the law. non-news.
If you follow the link in the pop-up, the BBC website explains that the changes will be phased in gradually over the Summer.
"The government's view is that there should be a phased approach to the implementation of these changes. Over the summer, we will be working on developing the best methods for obtaining your consent.
In the meantime, you can control cookies by setting your device to notify you when a cookie is issued, or not to receive cookies at any time. We will ensure that we continue to provide you with clear and comprehensive information about the cookies we use, so that you can make informed decisions."
On top of that, the law only covers tracking cookies, but the BBC is going to include all cookies in it's policy. No story here.
But there is a significant difference between a don't-show-message cookie and a we-know-everything-about-you cookie.
Privacy is terrorism.
CHUCK NORRIS doesn't need permission to set cookies in your system.
Nothing here... So... SHOOO!!!
In the UK, cookies are called biscuits.
nt
WARNING: Smartphones have side effects--most of them undocumented.
This law is an example of what happens when overly zealous do-gooders try to protect people from themselves. If you don't want cookies, turn them off.
Your Browser: Hey BBC, gimme a web page with the URI: http://raidotimes.com/
BBC Server: Here is the web page you requested, with cookie notification text (since you did not provide any cookie), and also a cookie.
Your Browser: Thanks! Let's see, the user settings say, "Accept Cookie" I'm permitted by the user to store this cookie.
--- Later ---
Your Browse: Hey BBC, gimme a web page [...] and also here's that cookie that you gave me which my user already gave permission for me to save and return to you via their preferences.
BBC Server: Ah, I see you provided me the cookie that if you had not given your browser permission to send me, I wouldn't be seeing right now -- I guess I won't show you that cookie info text this time.
YOU HAVE THE POWER TO DISABLE THE MOTHER FUCKING COOKIES -- USE IT AND STOP FUCKING UP OUR INTERNET WITH YOUR NOOB LAWS!
P.S. If the basic cookie settings aren't enough for you, use an existing plugin like Cookie Monster for Firefox -- More power over your god damn cookies than you could ever want. Honestly, if you don't understand it, leave it the fuck alone, before you hurt someone!
Not in this position, but the HTTP_REQUEST does include the language of the user's browser (accept-language)... It is fairly safe to assume that your site visitor wants it in the language that their browser is, and give them the option to change that language with a cookie to save it.
As an added bonus, if the site automatically looks at the accept-language and serves up a German-language storefront without the user having to click on German after being presented with an English default, it may improve your sales by not driving away some customers who may think your site isn't available in their language.
So I'll be like PC (http://www.adweek.com/adfreak/get-mac-security-94121) all the time, clicking Yes buttons when not needing them (while hating to see them), effectively priming me to approve one when I shouldn't.
Bert
.radiotimes.com LOG_ID 05/28/21
Google only goes up to 2013
.google.com PREF 05/27/13 ID= ******
See also, Radio Times recommends Internet Explorer 8
The UK's Information Commissioner issued some advice which isn't really finished but provides a good starting point. The big problem is that we don't have a good enough definition of what "strictly necessary" for the function of the site means. I've seen it interpreted (I think it was by a spokesman for the European Commission, but I didn't make a note at the time) as meaning cookies needed to perform a function requested by the user. The example given was a shopping cart - the user requests you to put an item in the cart, so you don't need to ask permission to use a cookie to associate that cart with the user.
Third party analytics software seems to be the target they're really shooting for, so I think we're going to have to move towards asking permission for those.
My personal opinion would be that the html standards needs to be changed. One change would be to create a session header, that does not write, and is cryptographically modified after each page access. This would prevent the websites from accidently storing session data, such as the recent linkedin session problem. Also I would change this so that only one session may be stored unlike cookies.
Cookies then can be used for what they were intended, the storage of information relating to the site, such as preferences. This then can be user definable as if you want to store them, not store them, not accept them, etc.
By which you mean "served via the Akamai caching network, which happens to use Linux". You might want to pick an example which is actually true.
For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
How come I can't set my browser to detect what type of cookie it is and prompt me if a site wants to set a tracking cookie? Get that accomplished and... problem solved.
It's just cookies, who ever complained about cookies?
Maybe we could require sites to provide milk if the serve any more than a couple of cookies...
If what I just said sounded like a troll, it was probably just a failed attempt at humor.
I guess this comes from the Department of Redundancy Department.
The mind conceives, the body achieves, the spirit manifests.
Mod parent up, submitter / "editors" didn't check their facts as per usual.
I'm glad this is the case since I still haven't had a response from our company's webhost as to whether the session cookies our site sets are needed for the stats package, or just an unneccessary ASP default setting.
I really hope it doesn't try to guess by working it out from the client's IP address.
Because if it does, I hate you.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Are session cookies OK?
I asked the ICO (Information Commissioner Office) exactly that question about a month ago, they have not replied in spite of a reminder. If they cannot answer a simple question like that then I have to assume that they don't know what they are talking about.