Did you cut the access to the firefox telemetry server (via PiHole i assume) before setting the parameters?
It could be Firefox trying to inform the telemetry server to not keep the data and/or logging the fact that you have disabled the telemetry.
A community for Lemmy users interested in privacy
Rules:
Did you cut the access to the firefox telemetry server (via PiHole i assume) before setting the parameters?
It could be Firefox trying to inform the telemetry server to not keep the data and/or logging the fact that you have disabled the telemetry.
It seems to have worked!
Firefox made these 5 connections:
telemetry-incoming.r53-2.services.mozilla.com
push.services.mozilla.com
firefox.settings.services.mozilla.com
content-signature-2.cdn.mozilla.net
firefox-settings-attachments.cdn.mozilla.net
...and then it shut up.
I will try to let the connection through and report back if it tries to connect again. Thanks for the advice, it sounds like a good idea.
I just checked my firewall logs and librewolf (at least with my current settings) does not attempt to connect to incoming.telemetry.mozilla.org
That's expected as LibreWolf aims to disable any tracking and telemetry innately, but it does not really answer my question. Thanks for your input though!
I was aiming at the "How do I stop it" question. - Either use librewolf, or compile a custom version of firefox applying whatever librewolf does to disable that.
But are you not already stopping it with your firewall?
It is true I am stopping it. But I would like to understand the reasons why FF is making this connection despite disabled telemetry.
Switch to Librewolf