- From: Jim Bursch <
>
- To:
- Subject: [projectvrm] DNT question
- Date: Wed, 08 Aug 2012 08:30:18 -0700
I haven't been paying close attention to the DNT discussion, so this may be a dumb question. It's
also more of a technical question.
Isn't tracking a function of cookies? So, killing cookies will kill tracking.
Am I wrong?
If I routinely and frequently delete cookies, I am performing my own DNT --
is that correct?
I have started doing that, but it is inconvenient mainly because of the poor choices for cookie
management, which is a browser problem.
Again, if I am correct that tracking is a cookie management problem, here is what I would want in a
cookie management system:
1. Clear, standard descriptions of the purpose of a given cookie. I want to know if it is a tracking
cookie, or an authentication cookie, or a data storage cookie, etc. Right now I can only guess at
the purpose of a cookie, given its content.
2. I want to be able to flag cookies that I would like to keep (e.g. authentication so I don't have
to repeat login), and flag cookies that I don't want (e.g. tracking cookies).
3. I want to be able to create different rules for how different cookies are handled, based on their
function/purpose -- e.g. keep cookies I like, delete cookies I don't want automatically.
It seems to me that the cookie management system would be a simple browser plugin in the short term.
The problem would be establishing a protocol for cookie meta data (type, function, purpose, etc.)
Am I over-simplifying?
Jim Bursch
310-869-5340
Headspace.info: Video Arts and Entertainment Directory
http://headspace.info
Producer
NoHo20 presents: "Critic's Dilemma"
http://noho20.com
Archive powered by MHonArc 2.6.19.