- From: Kevin Smith <kevsmith@adobe.com>
- Date: Sun, 22 Jan 2012 22:40:42 -0800
- To: David Singer <singer@apple.com>
- CC: Jonathan Mayer <jmayer@stanford.edu>, "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
I don't get it - I am still not sure what the concern is. The list of 3 motivations below seems like a good starting point. What I would like to know is: how does the party approach address these concerns, and why do you think the cross-tracking approach would not. They have nearly identical results in my opinion, so I would think they would equally meet (or fail to meet) these objectives. -----Original Message----- From: David Singer [mailto:singer@apple.com] Sent: Sunday, January 22, 2012 9:43 PM To: Kevin Smith Cc: Jonathan Mayer; public-tracking@w3.org (public-tracking@w3.org) Subject: Re: cross-site tracking and what it means On Jan 22, 2012, at 12:24 , Kevin Smith wrote: > >> Third, it does not go far enough in addressing consumer privacy risks. In our proposed non-normative discussion of first vs. third parties, Tom and I identified three motivations for the distinction: user awareness and control of information sharing, market incentives for privacy and security, and collection of data across unrelated websites. The "cross-site tracking" approach only somewhat mitigates the third concern and does nothing to address the first two. > > I agree with David here. I am not entirely sure what you mean. The two approaches have nearly identical results as far as the consumer is concerned so how would the party approach address these concerns, but the cross tracking approach fall short? Hang on, I absolutely share Jonathan's concerns with (why I understand to be) your formulation. I would need to se much more detailed rules about what can be recorded, and agree to them, before I would be comfortable. The alternative I formulated seems better, IMHO. David Singer Multimedia and Software Standards, Apple Inc.
Received on Monday, 23 January 2012 06:41:31 UTC