Text 1723, 196 rader
Skriven 2005-01-02 16:50:38 av Rich (1:379/45)
Kommentar till text 1719 av Mike N. (1:379/45)
Ärende: Re: Usage history
=========================
From: "Rich" <@>
This is a multi-part message in MIME format.
------=_NextPart_000_019B_01C4F0EB.2FF2F950
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cookies can not be PII unless you supply the PII. That makes them =
interesting for marketing purposes but meaningless to identify someone. = And
still, it is the client wholely in control. I never persist = doubleclick
cookies. In my usage I never honor them at all.
Contrary to what you say, identifying yourself in a purchase does not =
make their history available to doubleclick. If your purchase is not = from
doubleclick then they have no clue a purchase occured at all unless = the folks
from whom you are purchasing are giving away or selling your = PII. Similarly,
the folks from whome you purchase, unless doubleclick = itself, have no idea
what your doubleclick identity is unless = doubleclick is providing this to
them. And even if all this happened, = you can just delete your local cookies
and any cookie only identity goes = away.
I don't know why you mentioned jetblue or claim they were fingered by =
cookies. The story to which you refer makes no such claim. It's claims = are
quite clear and quite different.
Rich
"Mike N." <mike@u-spam-u-die.net> wrote in message =
news:vqrgt0dte9q55j7bq5bbuoi230b6f5cu2v@4ax.com...
On Sun, 2 Jan 2005 13:17:36 -0800, "Rich" <@> wrote:
> All this is paranoia about what someone could do and has never =
been about what actually is done.
>
> Continuing with your paranoia, cookies and auth events are not =
available in any single location. Cookies require you to go to each and =
every client,
Central ad servers such as DoubleClick are repositories for cookie =
and
individual tracking information through the referrer and =
site-specific ad
trigger. Now whenever someone identifies themselves through a =
purchase,
their entire personally-identifiable history is available from =
DoubleClick.
This is the default cookie configuration which 95% of the population =
never
adjusts or purges. So while cookie information is not available in =
any
single location, it takes only collaboration by 2-3 sites to reveal =
all
the cards.
Continuing onto what has actually been done: 1,500,000 people have =
been
fingered by cookies under the guise of Homeland Security - Airline
Passenger Risk Assesment.
http://www.computer.org/security/V2n6/anton.htm
"Torch's homeland security report explains that it matched the JetBlue
passenger information database with information purchased from Acxiom =
to
determine gender, home specifics (renter or owner), years at =
residence,
income, number of children, adult SSNs, occupations, vehicles owned, =
and so
on, for 40 percent of the passengers in the database.2 Torch leveraged =
the
information JetBlue provided (which it claimed was limited) into a =
much
larger information corpus by purchasing demographic information from =
Acxiom
to augment the database."
It took only 4 organizations: JetBlue, Acxiom, ???(unknown 3rd =
party),
and Torch to pull off this fiasco. =20
------=_NextPart_000_019B_01C4F0EB.2FF2F950
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.1289" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2> Cookies can not be PII =
unless you=20
supply the PII. That makes them interesting for marketing purposes =
but=20
meaningless to identify someone. And still, it is the client = wholely
in=20
control. I never persist doubleclick cookies. In my usage I =
never=20
honor them at all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Contrary to what you say, =
identifying=20
yourself in a purchase does not make their history available to=20
doubleclick. If your purchase is not from doubleclick then they = have
no=20
clue a purchase occured at all unless the folks from whom you are = purchasing
are=20
giving away or selling your PII. Similarly, the folks from whome = you=20
purchase, unless doubleclick itself, have no idea what your doubleclick =
identity=20
is unless doubleclick is providing this to them. And even if all =
this=20
happened, you can just delete your local cookies and any cookie only =
identity=20
goes away.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> I don't know why you =
mentioned jetblue=20
or claim they were fingered by cookies. The story to which you = refer
makes=20
no such claim. It's claims are quite clear and quite=20
different.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Mike N." <<A=20
href=3D"mailto:mike@u-spam-u-die.net">mike@u-spam-u-die.net</A>> =
wrote in=20
message <A=20
=
href=3D"news:vqrgt0dte9q55j7bq5bbuoi230b6f5cu2v@4ax.com">news:vqrgt0dte9q=
55j7bq5bbuoi230b6f5cu2v@4ax.com</A>...</DIV>On=20
Sun, 2 Jan 2005 13:17:36 -0800, "Rich" <@>=20
wrote:<BR><BR>> All this is paranoia about what someone =
could=20
do and has never been about what actually is =
done.<BR>><BR>> =20
Continuing with your paranoia, cookies and auth events are not =
available in=20
any single location. Cookies require you to go to each and every =
client,<BR><BR> Central ad servers such as DoubleClick are =
repositories=20
for cookie and<BR>individual tracking information through the =
referrer=20
and site-specific ad<BR>trigger. Now whenever someone =
identifies=20
themselves through a purchase,<BR>their entire personally-identifiable =
history=20
is available from DoubleClick.<BR>This is the default cookie =
configuration=20
which 95% of the population never<BR>adjusts or purges. So =
while=20
cookie information is not available in any<BR>single location, it =
takes=20
only collaboration by 2-3 sites to reveal all<BR>the=20
cards.<BR><BR> Continuing onto what has actually been done: =
1,500,000=20
people have been<BR>fingered by cookies under the guise of Homeland =
Security -=20
Airline<BR>Passenger Risk Assesment.<BR><BR><A=20
=
href=3D"http://www.computer.org/security/V2n6/anton.htm">http://www.compu=
ter.org/security/V2n6/anton.htm</A><BR><BR>"Torch's=20
homeland security report explains that it matched the =
JetBlue<BR>passenger=20
information database with information purchased from Acxiom =
to<BR>determine=20
gender, home specifics (renter or owner), years at =
residence,<BR>income,=20
number of children, adult SSNs, occupations, vehicles owned, and =
so<BR>on, for=20
40 percent of the passengers in the database.2 Torch leveraged=20
the<BR>information JetBlue provided (which it claimed was limited) =
into a=20
much<BR>larger information corpus by purchasing demographic =
information from=20
Acxiom<BR>to augment the database."<BR><BR> It took only 4=20
organizations: JetBlue, Acxiom, ???(unknown 3rd party),<BR>and Torch =
to pull=20
off this fiasco. <BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_019B_01C4F0EB.2FF2F950--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|