See comment https://github.com/ghacksuserjs/ghacks-user.js/issues/103#issuecomment-300911966 - `*safebrowsing.provider.mozilla.*` is for Flash & TP ONLY (original article by francois had a *slight!!* error since fixed)
This means that 0410d was not shared by TP and SB and to clear it all up .. 0410d is moved to 0420's. 0420's also gets the flash pref 0440 moved into the 0420's.
Now it's all tidy: 0410's = google and SB, 0420's = mozilla & TP+Flash
Exception: I am enforcing TP in ALL windows (default is PB Mode only). I have also added the info for which block list to use in TP. Also clarified that 0440 (flash blocklist) uses prefs in 0410d. Also made flash tracking blocklist pref (0440) inactive. Now all TP and SB is allowed, only real time google binary checks and reporting is disabled.
Instead of `geo.wifi.uri` using 127.0.0.1, for those who do use geo (`geo.enabled` is the master switch), enforce Mozilla's service over Google's.
- Default in stable, beta: https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY%
- Nightly defaults to mozilla (not usre of the exact string)
- I do not know if this is a telemetry thing for mozilla for non-stable or if this will roll down from nightly
default is false anyway. We can readdress this if it ever gets turned on, or used for purposes other than ad networks - I suspect there's nothing really out there using it right now, and the fact 53 is false, I bet there's no big hurry to turn it on due to stability and real world usage.
its added as default false, but looks like we'll need to check out what options the two prefs (dom from 51 and browser from 53) when true show in the options UI
The blog entry [2] and subsequent ticket [3] are new.
Francois mentioned the older ticket [4].
FYI: `device.sensors.enabled` was introduced in FF15 (don't think I need to add that in)