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