- From: Alan Chapell <achapell@chapellassociates.com>
- Date: Tue, 09 Jul 2013 13:44:47 -0400
- To: John Simpson <john@consumerwatchdog.org>, Walter van Holst <walter.van.holst@xs4all.nl>
- CC: <public-tracking@w3.org>
Thanks John. Over the years, there have been a number of entities that have obtained URL strings from browsers and other UA's and used those for tracking. (e.g., a handful of companies were dinged for obtaining URL strings from certain browsers via javascript). Some of my colleagues at browser companies have referred to this as "leakage." I think that term is close enough so long as we all agree that leakage would include a UA's proactive transfer of information based upon URL history to an outside entity. Alan On 7/9/13 1:26 PM, "John Simpson" <john@consumerwatchdog.org> wrote: >Alan, > >Include me as confused, too. I don't see how a user agent is doing >tracking unless it reports back to the browser manufacturer. Is that >what you mean? Can you please give some specific use cases? >Thanks, >John > > >On Jul 9, 2013, at 7:45 AM, Walter van Holst <walter.van.holst@xs4all.nl> >wrote: > >> On 2013-07-09 16:23, Alan Chapell wrote: >> >>> RATIONALE: >>> In reviewing the June draft with colleagues, it occurred to me that >>> some User Agents - technically speaking - could engage in tracking. My >>> sense is that it is implicit that User agents would fall under the >>> definition of third party under this spec and therefore would be >>> subject to certain requirements. My goal was to make that more >> >> This is confusing to me. Unless we are talking about certain "search >>bar" browser extensions that are essentially spyware, it is not obvious >>to me what kind of user agents you mean by this. >> >> Regards, >> >> Walter > > >
Received on Tuesday, 9 July 2013 17:45:25 UTC