Mozilla fucking up like this still feels like a friend fucking up. It's frustrating and disappointing precisely because I expect Mozilla to be better than this.
Why was this not done in the first place?
If you do decide to come clean, it would help a lot if you gave assurances about what you have learned and how you will change the process so that this doesn't happen again. Trust is difficult to gain and easy to lose.
I must say I am sorry to see all this happening though. I have always hated Chrome (a bit less than IE, but for other reasons) and am (still) your loyal user. I even enabled telemetrics recently (which means _a lot_ - there is no other piece of software that gets this willingly from me) - needless to say, they are turned off again. We'll see how the postmortem turns out.
was it a candid easter egg ?
I feel a bit distanced about the whole situation. The issues I've seen are:
- getting money from secret extension - potential security risk - bad will from mozilla
the name shield studies feels a bit scary, a CIA paranoia tone but anyway.. I believe that's the era that is tense and what seems to be an easter egg as you say, ends up as a brutally negative thing.
And it's not like we have any massive problems to unite against (that we can actually feel like we can help with).
That’s a very dangerous type of justification there, not one I expected someone at Mozilla to get that wrong.
You could argue technicalities for either, but semantically, it's off by default.
The add-on is implemented as an "embedded webextension" which is wholly contained by an outer "bootstrapped add-on." The bootstrapped add-on controls whether or not the embedded webextension gets initialized, and that's all it does.
The bootstrapped add-on is literally just this one file: https://github.com/mozilla/addon-wr/blob/59659431fd2a75c33ac...
The outer shell is on by default. The embedded webextension is only initialized by the bootstrapped add-on if the user manually flips the "extensions.pug.lookingglass" preference in about:config. That preference is off by default.
> why not just have the user actually install the extension at the time of consent, rather than prefetching?
That's what we're moving to by pulling the add-on from Firefox and posting it on AMO.