31–40 of 480 posts
> This will allow us to track which installs result from which downloads to determine the answers to questions like, "Why do we see so many installs per day, but not that many downloads per day?" What value does Mozilla see in being able to do that?
> This will allow us to track which installs result from which downloads to determine the answers to questions like, "Why do we see so many installs per day, but not that many downloads per day?" What value does Mozilla see in being able to do that?
Why would this be important, again just speculating: to try to leverage whatever channel this might uncover to distribute even more copies of the browser.
Is this ID thing the best way to do it, though? Probably.
how does this get through the MS smartscreen and authenticode checks?
I don't really understand telemetry. How is Google Analytics helping them to improve the browser? Is it to see which features are actually being used?
Package manager installations wouldn't have this problem because everybody gets the same copy of the same binary and associated files, rights?
Correct and it's just one of many reasons why checksums and signatures are so important in package managers. There's an automatic enforcement of privacy and integrity.
OK, however, are we completely sure that Chrome installer doesn't generate this token on launch and talk with the mothership?
This sounds like whitewashing Chrome just to increase the impact of the article or push Chrome or both.
Like Chrome is not tracking me in and out of the internet and in the kitchen making tea and noting its brand and reporting to Google.
It's like discovering there's ham in a vegetarian sandwich. When you ask them they look puzzled and say their focus group was clear it tastes a lot better that way, besides it's just a little bit and the bread is vegetarian and there's way more meat in a Big Mac.