From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
Date: Tue, 25 Sep 2018 06:02:48 -0500 [thread overview]
Message-ID: <ebd15d02-13bb-b090-575c-276e50524831@gmail.com> (raw)
In-Reply-To: <2155865.pBUWVHprkz@dell_xps>
Mick wrote:
> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
>> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
>>
>>> This is worse than I expected. OK, therefore never signing into Google's
>>> systems with Chromium is the only way to stop this invasion of privacy.
>>> Thankfully, we still have Firefox. ;-)
>> Ahemm...
>> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firef
>> ox.html
> Yes, there is this leaking agent running in FF, but I have (almost) disabled
> telemetry. The problem is this pesky entry which is shown as "locked" and
> therefore unable to be disabled in about:config
>
> Preference Name Status Type Value
> ========================= ====== ======= =====
> toolkit.telemetry.enabled locked boolean true
>
Just for giggles, I looked at my config and it shows a default status
and is set to false. Maybe it is a difference in version or could it be
a USE flag makes a difference or something else??? I'm on Firefox
52.9.0. Maybe you are using the latest version. I'm stuck here due to
some add ons not ready for the newer versions.
Dale
:-) :-)
next prev parent reply other threads:[~2018-09-25 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 6:47 [gentoo-user] OT: Noteworthy change in the way Chrome logs in Adam Carter
2018-09-24 7:09 ` Andrew Udvare
2018-09-24 10:29 ` Mick
2018-09-24 12:47 ` Andrew Udvare
2018-09-24 13:59 ` Mick
2018-09-25 2:11 ` Walter Dnes
2018-09-25 10:51 ` Mick
2018-09-25 11:02 ` Dale [this message]
2018-09-25 11:12 ` Mick
2018-09-25 12:29 ` Dale
2018-09-25 15:14 ` Mick
2018-09-24 14:20 ` [gentoo-user] " Nikos Chantziaras
2018-09-24 21:09 ` Andrew Udvare
2018-09-24 23:17 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ebd15d02-13bb-b090-575c-276e50524831@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox