[1] https://mobile.twitter.com/meatcomputer/status/8813107782251... [2] https://github.com/mozilla/addons-frontend/issues/2785#issue...
[1] https://mobile.twitter.com/meatcomputer/status/8813107782251... [2] https://github.com/mozilla/addons-frontend/issues/2785#issue...
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.
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.
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?
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.
Note that old-style extensions do work and currently still block this.
3. that a part of the browser chrome (which is technically iframing a website, but should still meet user expectation of being a part of the browser) is tracking users who have explicitly opted out of browser telemetry.
4. that in-browser telemetry includes sending user data to 3rd-parties without that being explicitly consented to.
Tbh, AMO using GA is something I don't really find acceptable, and would much rather was phased out, but having been aware of it for so long, it'll hardly drive me away. Most importantly, I can block it with an addon (unlike this issue).
Really though, the crux of the issue here from a PR perspective is not any individual technical failing, but the really disappointingly dismissive attitude of the Mozilla devs replying to comments on Github and here. If an employee of Mozilla can't see the significance of this, I worry about Mozilla's adherence to it's own stated mission.
They should stop that now after this PR disaster.
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.
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.
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.