1 |
On Tuesday, 25 September 2018 12:02:48 BST Dale wrote: |
2 |
> Mick wrote: |
3 |
> > On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: |
4 |
> >> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote |
5 |
> >> |
6 |
> >>> This is worse than I expected. OK, therefore never signing into |
7 |
> >>> Google's |
8 |
> >>> systems with Chromium is the only way to stop this invasion of privacy. |
9 |
> >>> Thankfully, we still have Firefox. ;-) |
10 |
> >> |
11 |
> >> Ahemm... |
12 |
> >> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-fir |
13 |
> >> ef |
14 |
> >> ox.html |
15 |
> > |
16 |
> > Yes, there is this leaking agent running in FF, but I have (almost) |
17 |
> > disabled telemetry. The problem is this pesky entry which is shown as |
18 |
> > "locked" and therefore unable to be disabled in about:config |
19 |
> > |
20 |
> > Preference Name Status Type Value |
21 |
> > ========================= ====== ======= ===== |
22 |
> > toolkit.telemetry.enabled locked boolean true |
23 |
> |
24 |
> Just for giggles, I looked at my config and it shows a default status |
25 |
> and is set to false. Maybe it is a difference in version or could it be |
26 |
> a USE flag makes a difference or something else??? I'm on Firefox |
27 |
> 52.9.0. Maybe you are using the latest version. I'm stuck here due to |
28 |
> some add ons not ready for the newer versions. |
29 |
> |
30 |
> Dale |
31 |
> |
32 |
> :-) :-) |
33 |
|
34 |
I'm on 60.2.0 and although other telemetry entries are modifiable, the one I |
35 |
mention above is shown as locked. Apparently this is locked to 'true' for |
36 |
pre-release builds and 'false' for release builds: |
37 |
|
38 |
https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5 |
39 |
|
40 |
-- |
41 |
Regards, |
42 |
Mick |