4 ms·
Given Firefox's pro-privacy positioning vs Chrome [1] and the fact that, by virtue of being in about: these requests get sent even if the user is browsing in pr
by michaelt 9y ago
Given Firefox's pro-privacy positioning vs Chrome [1] and the fact that, by virtue of being in about: these requests get sent even if the user is browsing in private browsing mode or has extensions installed explicitly to block this kind of traffic [2] it's surprising the Mozilla employees in that thread are so keen to dismiss this.
[1] https://mobile.twitter.com/meatcomputer/status/881310778225172480 https://mobile.twitter.com/meatcomputer/status/8813107782251...
[2] https://github.com/mozilla/addons-frontend/issues/2785#issuecomment-314807534 https://github.com/mozilla/addons-frontend/issues/2785#issue...
- shallot_router 9y ago@tofumatt's responses sound pragmatic but very tone-deaf given Mozilla's privacy stance. I feel like the only right answer here is to tie all of this into the telemetry opt-in and don't load GA if the user hasn't opted in.
- lucideer 9y agoThe problem with that approach is that, many technically literate Firefox users will deliberately opt-in to Telemetry as a component of their support for a pro-privacy product. Telemetry actively benefits development of Firefox, and a pro-privacy user will want to strategically share their data with entities they trust in order to row back against the tide of entities that they do not trust. Frankly, Mozilla are shooting themselves in the foot by sending any data from any of their products or web properties to their primary competitor.
- gcp 9y agoThe problem here is that GA is quite frankly Telemetry For Websites. Frankly, Mozilla are shooting themselves in the foot by sending any data from any of their products or web properties to their primary competitor. This ship sailed a long time ago. Mozilla negotiated stricter privacy in their contracts with Google, and Mozilla Legal clearly believes Google will uphold those agreements despite it being a competitor.
- microwavecamera 9y agoBut it begs the obvious question, why use Google Analytics at all? If it's just about gathering statistics there's several non-invasive ways to acquire that data.
- gcp 9y agoApparently it's an awesome product. I stopped using it myself because I didn't want to deal with EU cookie notices, which is why I'm surprised to see claims here they are compatible with EU cookie laws.
- lucideer 9y ago> This ship sailed a long time ago You may be right, but I hope not. The fact Mozilla negotiated stricter privacy in their contracts is a step in the right direction, so this shows some desire to improve. It needn't be the final step. Beyond that, there are other areas where there's been similar change. The Mozilla Stumbler project, for example, is explicitly designed to improve user choice in a privacy-sensitive area dominated by a Google service; a service that was embedded in Safari, Firefox and Opera 12 (Presto) for a long time without users being aware their browser was phoning home to Google. I would hope this GA fiasco could someday be similarly resolved with enough user pressure.
- gcp 9y agoSending these requests with TP enabled (i.e. in private browsing) is a plain bug as far as I'm concerned.
- rdtsc 9y agoGranted disguising things as a bug is also one of the sneakier and better ways to implement the feature if that was the intent to begin with ;-)
- potch 9y agoGiven that the discussion in the issue is "hey let's use DNT/tracking protection as a signal to not load this", assume we're looking at a reasonable mitigation here and that this was at worst an oversight.
- gcp 9y agoIt's more that the people implementing and reviewing the feature (cough) didn't expect about:* pages to end up loading frigging Google Analytics.
- gcp 9y agoCalled it: https://bugzilla.mozilla.org/show_bug.cgi?id=1380448#c4 https://bugzilla.mozilla.org/show_bug.cgi?id=1380448#c4
- ssivark 9y agoI can understand @tofumatt's desire to restrict that Github thread to the specific problem and its fix. However, given Mozilla's recent advertizing attempts slinging mud at Google/Chrome, it seems like they're asking for their credibility to be shredded publicly, in the media. This is an important enough matter that it deserves immediate escalation, to get a clear and coherent response at the organizational level that is communicated convincingly to users. Anything short of that (especially a simple local bug fix) risks winning the battle but losing the war, as Firefox's fundamental selling point now seems duplicitous and disingenuous. I sincerely hope that Mozilla/Firefox developers have the vision to recognize that, and consider this matter of utmost importance. All the features and technical improvements they might hope to ship in the next several months are irrelevant compared to this single issue. To me, this debate is a great example of a situation where an organization must be guided by its core principles -- not by what seems convenient in each specific instance.
- gcp 9y agoAll the features and technical improvements they might hope to ship in the next several months are irrelevant compared to this single issue. Which "single issue" is that then? That AMO is using GA (and has been for years)? Or that TP doesn't work correctly for the in-browser UI? I'm going to have to disagree with you there.
- ssivark 9y agoThey are both issues. My principal point is that they're all part of the same problem in the bigger picture, which is: Mozilla is breaking its privacy promises to its users. 1. Mozilla casts aspersions on Google/Chrome for not respecting users' privacy. (eg: recent billboard advertizements) 2. Mozilla doesn't respect users privacy because it uses tracking, that too third-party, that too from Google. Pot -> kettle -> etc... Mozilla risks losing credibility. What fundamental principles do they claim to stand for, if they're willing to compromise those for convenience?
- gcp 9y agoSiloing the GA data that is obtained from Mozilla (required by the contract Mozilla has with Google) would stop the privacy-breaking aspects (which exist due to aggregating over sites). But this may be a case where even though Mozilla is technically doing the right thing, perceptions will tend the opposite way. Without that statement in that old bug, most people would never know the Mozilla GA data is siloed.