New issue
Advanced search Search tips

Issue 1813 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2008
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

Unique Identifier generated for each installation

Reported by ralph.so...@imixs.com, Sep 8 2008

Issue description

Product Version      : chrome

chrome seems to generate a unique identifier (uniqueid) for each
installation instance. So the browser instance can be identified uniquely
by a server or other programms.
I think the id should be generic and unique only over the code module
itself. In Eclipse such ids are also used but only for a single plugin
(PluginID). This is in general very useful to identify the program module. 
Also in Maven generates uniqueIDs for each specific fragment.

So there should no unique id available for each installation. 
How can I change this?

thanks 
ralph
 
The id is currently stored into the file
..Chrome\User Data

under section: user_experience_metrics - 
client_id
Status: WontFix
This is by design, not a bug.

The user_experience_metrics ID cannot be generic. We need a different ID for each 
instance of the program so that statistics about one event (crashes, eg) can be 
correlated with other events (number of page loads).

I'm not sure why you'd want to change this.

Maybe you're just asking how you can turn it off/prevent Google Chrome from using it?
If so, open the Wrench menu > Options > Under the hood and uncheck "Help make Google 
Chrome better".




Comment 3 by brian@chromium.org, Sep 8 2008

There's a little confusion here that I'd like to clear up. There are two IDs being 
discussed. They are stored and used separately.

First of all, there is an installation ID (iid) which is created at install time to 
de-dup install counts. This is necessary to accurately count the number of successful 
installations that have occurred.  The iid is generated randomly (not based on any 
other information) and is deleted in the next update check after first run. 

There is a second ID called the clientID which is used for the user metrics service. 
This is an opt-in service that lets users send usage statistics to Google so that we 
can learn how the product is being used for the sake of making improvements. It helps 
us answer questions like, "Are people using the back button?" and "How common is it 
that people click the back button repeatedly?" Users can always update their 
preference about sending usage statistics on the "Under the Hood" tab of options.
ok - thanks for clarify this.
There is a similar new function in eclipse ganymede called "Usage Data Collector".
Eclipse asks each time before sending data and also it generates a log file where I
(the user) can see which data will be send to eclipse foundation. 
Can I see also the informations send out by chrome?
Would not be a similar control dialog meaningful for chrome to inform the user how
google will treat the data provided by individuals?
I second comment no 4 by Ralph, I wish Google would be more transparent in what sort of data it is uploading. 
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 12 2012

Labels: Restrict-AddIssueComment-Commit
Owner: ----
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Sign in to add a comment