#21 Remove Telemetry

I accidentally found that Firefox Health Report service (FHR) is enabled for Pale Moon (while it isn’t for Basilisk), because MOZ_SERVICES_HEALTHREPORT=1 is set by default in old-configure.in. I’m not sure if any data are actually sent to Mozilla, but at least it is recorded in saved-telemetry-pings and datareporting folders in the profile.

Since there is no release of any kind of Pale Moon on UXP yet, what is your issue?

Part of the first step to porting was to match configuration where possible to eliminate issues.. We know Mozilla has botched conditional status of platform components so working out those bits while trying to achieve basic buildablity work against each other.

Rest assured, this crap won’t stick around for long.

I’ve pushed a few conf changes in confvars so your precious data won’t be collected in a health report by default.

Thanks, this is exactly what I wanted to have until the telemetry is wiped off completely.

I understand that this will involve a lot of work.
..but shouldn’t this issue be tagged for the 28.0.0 release milestone?
Many users will probably want to stay with Tycho, until it has been resolved.

It’s not a release blocker. Telemetry is disabled -- actually removing it from the tree is something that will take time but is ultimately just code cleanup.

@THEtomaso, JFYI: Tycho also has Telemetry disabled, and not removed.

Thanks for clarifying, guys. :)

Another question though..
If it’s just a matter of code cleanup, why is this issue still labeled with “High Risk”, “Privacy” and “Security”?

The code removal is high risk because it is weaved into many things and can break functionality or impact security if not carefully removed. And it’s telemetry, so labeled with Privacy.

Note to self: remove PaintTelemetry from /layout.

There was #1074 which was closed. I would like to know, how could one fix this PR in order for it to be accepted?

@Kokokokoka By not doing everything in one single PR.
Do it step by step if interested, otherwise I’ll take care of it eventually (too busy at the moment).

It is getting very close to a defacto major stable release branch off point so hold off on this unless it is trivial.