RE: privacy definitions -- was: WebID questions

Furthermore you have to differentiate between cookies for different purposes, for example, advertising tracking, login information, certain kinds of state etc.

You have a catch-22 situation here, in order to give the user or consumer enough information about - in this case - cookie usage, the UI would become very complicated and the burden of understanding in the consequences and implications of certain cookies being turned on and off would be toó high; on the other hand, if you have a simple on/off then the repercussions on some basic functionality of sites would lead to a potentially (massively) degraded and frustrating user experience.

Does anyone have a reference to the typical amount of type of cookies stored by a "typical" user?

t.

Ian
________________________________________
From: ext David Singer [singer@apple.com]
Sent: 17 October 2012 09:17
To: Henry Story
Cc: Melvin Carvalho; Ben Laurie; public-privacy list; public-webid@w3.org
Subject: Re: privacy definitions -- was: WebID questions

On Oct 16, 2012, at 20:40 , Henry Story <henry.story@bblfish.net> wrote:

>
> But that is not yet transparency I am looking for. Because you could go to a site and click mistakenly on "accept cookies forever", and you could easily forget about it later. What is
> needed I was arguing is the ability to be able to see in your URL bar that you are using cookies
> and be able to switch it off easily. Then you would be made aware constantly of your identity at
> a site.

The problem is that many, if not most, sites use cookies, and a warning that is almost always on gets ignored.


David Singer
Multimedia and Software Standards, Apple Inc.

Received on Wednesday, 17 October 2012 06:30:52 UTC