Cookie law. Good intentions, bad implementation

Cookie law requires websites to place a confirmation notice if the website is using cookie technology. The "Cookie", in essence, is bit of data that websites store in browser. All browsers has to support it, because it is defined in web standards. On one hand, cookie functionality enables better site experience. On the other hand, it can be used to track users without them knowing.

The idea behind the law is to make users aware that this website is storing information into their browsers. However the solution of making every website in the world implement the dialogue is... let me see how can i put it - unrealistic

Much better solution would be making browsers to implement this functionality.

Here is a list of reasons why:
  1. If browsers are implementing this functionality users would be given possibility to opt out if they really don't want to be informed (YAY to that)
  2. If website is using cookies, browser knows about it, and therefore will show the notice on ALL websites using the technology. This would cover 100% websites with one go, and not rely on site owners to remember implementing the confirmation dialogue.
  3. It will save wast amount of development resources spent on building solutions for every website. Just imagine how many websites there are versus how many browsers there are. It will also save wast amount of controlling resources that monitor if the websites are following the law 
  4. Having information about cookies presented in the same manner for all websites would it make easier for users to perceive the information. It's much better than each website coming up with their own text and formatting.
  5. Solutions in browser can be made to show what information exactly is stored in browser, so user can make better decision. It gives me no value to know that website is storing something somewhere. However if I see that website is saving information about me that I'm not comfortable with, It might actually be useful and I might decide to not visit the website any more.
  6. It is easy to control which users should see the message and which not. The browser would just need to know if the user is in the affected territory (EU) or not.

Comments

Post a Comment

Popular posts from this blog

What does http-equiv stands for?

Many web developers uses meta http-equiv tag, without solid understanding what does it means. http-equiv stands for: hypertext transfer protocol equivalent and is equivalent to HTTP response header. So putting: <http-equiv="content-type" content="text/html; charset=UTF-8"> <META http-equiv="content-type" content="text/html; charset=UTF-8"> in HTML as meta TAG has the same effect as declaring HTTP response header Content-Type: text/html; charset=utf-8 That is why they are called ‘equivalent’. It is recommended to use HTTP header over HTML http-equiv meta tags. Multiple headers with the same name may be present only if the values may be concatenated.
Read more

How many water molecules are there in the glass of water?

Image
How many water molecules are in a glass of water? This glass is filled with 200 ml water. That is 0,2 l of water. First, to get started, we need to convert volume to mass. Since 1l water equals 1kg water, then our 200 ml glass is filled with 0.2 kg water. In school chemistry probably in 8th grade there was a term Mole. Mole is a unit and it measures number of molecules. One mole has 6.0221415×10 23 molecules in it. And another term is molar mass. The molar mass of an element is the atomic weight in grams per mole. In other words molar mass states - how much does one mole of particular substance weight. The molar mass for distilled water is 18 g/mol or converting to kg, it is 0,018 kg / mol. So, now lets do some calculations. First, let's calculate - how many moles of water there are in the glass. Moles = mass / molar mass = 0,2 kg / (0,018 kg/mol) = 11.11 moles And then, let's calculate how many molecules there are in the 11.11 moles Number of molecules = number of mols * m
Read more