3 ms·
They 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
by ssivark 9y ago
They 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.
- michaelt 9y agoSiloing, schmiloing. If the user has installed an extension that blocks Google Analytics, and you disable that extension, you're clearly ignoring the user's privacy choices.
- gcp 9y agoWebExtensions are never active on about:* pages, that's a documented design choice not specific to content blockers or GA or whatever. Note that old-style extensions do work and currently still block this.