Re:Chrome sends a suspicious tracking parameter on every Goo...
by hrjet on Saturday November 09, 2013 @08:00AM
(#6701512)
The autocomplete timings are one part of it. I am more concerned about other parts which are not publicly documented and seem to contain possibly identifiable information. I will be very happy if my suspicions are proven unfounded.
Aside, there seems to be an RLZ parameter in Chrome, which is purportedly absent from Chromium. The RLZ parameter comes from [1], which according to that page is now integrated into Chromium. By manual inspection of the AQS parameter value, there seems to be some identity of the browser included in it.
Re:Chrome sends a suspicious tracking parameter on every Goo...
by lampe3 on Saturday November 09, 2013 @07:34AM
(#6701457)
if you click on the var you get on this page:
https://code.google.com/p/chromium/codesearch#chromium/src/c...
ther is a link with more details: http://goto.google.com/binary-clients-logging
but for that you have to login with a google employ account...
Re:Chrome sends a suspicious tracking parameter on every Goo...
by pearjuice on Saturday November 09, 2013 @08:12AM
(#6701529)
Heh, that login page is marked up with a tabular layout. I wonder why Google as a "cool-kid" company never properly redesigned its internal applications. I can only shudder at the usability of "moma". Or is it just the login page?
https://code.google.com/p/chromium/codesearch#chromium/src/c...
https://code.google.com/p/chromium/codesearch#chromium/src/c...
Looks harmless enough. It just provides omnibox autocomplete timings to search engines.