possible additions related to telemetry and datareporting

[berrythesoftwarecodeprogrammar]

toolkit.telemetry.unified -> false
toolkit.telemetry.unifiedIsOptIn -> true
toolkit.telemetry.archive.enabled -> false i looked in my profile folder and found that it was storing things in a folder called /saved-telemetry-pings/
toolkit.telemetry.server -> ""
experiments.manifest.uri -> ""
toolkit.telemetry.cachedClientID -> ""
datareporting.policy.dataSubmissionEnabled -> false
datareporting.healthreport.pendingDeleteRemoteData -> false
datareporting.sessions.currentIndex -> 0 or "0"? in one of my firefox's its a string and in one its an integer lol
datareporting.sessions.prunedIndex -> 0
experiments.enabled -> false
experiments.supported -> false

sources:
https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/preferences.html
https://wiki.mozilla.org/QA/Telemetry/AboutPreferences
my about:config

you might wanna search your about:config for 'datareporting' and 'telemetry'. mine had a lot of weird datareporting session things saved which i removed. also check the /datareporting/ folder in your profile folder. it seems to be recreated and files written even when these features are disabled? i added them to ccleaner and also the /saved-telemetry-pings/ folder. its worth it checking your profile folder for unnecessary/weird files and folders if your profile is as old as mine.

[berrythesoftwarecodeprogrammar]

yeah, those are just things i did, some was to clean up my own profile. i just wrote about all of it so you more experienced users can figure out which ones should be put in to user.js because i think some of those prefs might be useful.

and its odd that firefox keeps creating files related to these features even when they are disabled

[pyllyukko]

Ok, so I set toolkit.telemetry.unified to false. I think that should be enough.

The gecko link states that "toolkit.telemetry.enabled: If unified is off, this controls whether the Telemetry module is enabled."

[pyllyukko]

I'm closing this now, as setting .unified and .enabled to false should kill the whole telemetry system. Re-open this if you disagree or have some other additional info.

BTW. As @CHEF-KOCH said, there's no point in setting every single setting (which is a lot!) that somehow relates to some feature, but only the "main switches".

So as an analogy: if I want silence and I power off my amplifier, there's no need to touch the volume control anymore, as it's not powered on anymore and there's no sound anyway.

@berrythesoftwarecodeprogrammar: Thanks for raising the issue.

[berrythesoftwarecodeprogrammar]

are the experiments and datareporting values taken care of already too?

[pyllyukko]

Well at least health reporting should be. Experiments is not set. I will check this...

[pyllyukko]

are the experiments and datareporting values taken care of already too?

Well now they should be dealt with, so I'll close this (again).

[pyllyukko]

toolkit.telemetry.unified

It's default true and we can leave it, because we entirely removed any telemetry so we not need to touch it.

Well actually... according to the links provided by @berrythesoftwarecodeprogrammar, it seemed that setting only toolkit.telemetry.enabled was not enough.