3 ms·

This brings up the questions: How can i disable as much telemetry as possible when using the standard Firefox? What am i missing if i go to <about:config>, sea

by Tepix 5y ago

This brings up the questions: How can i disable as much telemetry as possible when using the standard Firefox? What am i missing if i go to <about:config>, search for "telemetry" and set everything to false? Are there drawbacks to blocking the hostname incoming.telemetry.mozilla.org in Pi-hole?

freddref 5y ago
Surely there's a way of scripting this... Something like this: https://github.com/shawnanastasio/firefox-privacy-restorer https://github.com/shawnanastasio/firefox-privacy-restorer
toastercat 5y ago
https://github.com/arkenfox/user.js https://github.com/arkenfox/user.js
- johnisgood 5y ago
  There is https://gist.github.com/MrYar/751e0e5f3f1430db7ec5a8c8aa237b72 https://gist.github.com/MrYar/751e0e5f3f1430db7ec5a8c8aa237b... as well (check out the comments, too). Or https://gist.github.com/davinian/1991bb3486cbf6005b5320e93b3f94d2 https://gist.github.com/davinian/1991bb3486cbf6005b5320e93b3... but it is quite old I think. In any case, make sure you know what you are disabling, because in the latter it suggests disabling WebSockets which you may not want to do.
Communitivity 5y ago
Supposedly this will opt you out: https://support.mozilla.org/en-US/kb/telemetry-clientid https://support.mozilla.org/en-US/kb/telemetry-clientid One way is to use your firewall to block anything going to mozilla.org or firefox.com, or the subdomains. That probably gets most of it, but possibly not all. For example, Google has a number of non-Google.com subdomains, some of which seem to be used only for telemetry. Another more involved way is to start WireShark or tcpdump and capture the traffic, then start Firefox and browse some, and then close Firefox and stop the capture. Now you have a list of all the traffic it tries to send, normal and telemetry. Sift out anything that looks suspicious and block the ip/domain via your firewall.
dveditz_ 5y ago
Or you just turn it off in the normal preference UI and trust that California's AG will sue Mozilla into oblivion if they weren't honoring the CCPA. https://blog.mozilla.org/netpolicy/2019/12/31/bringing-californias-privacy-law-to-all-firefox-users-in-2020/ https://blog.mozilla.org/netpolicy/2019/12/31/bringing-calif...

by Tepix 5y ago

freddref 5y ago

Surely there's a way of scripting this... Something like this: https://github.com/shawnanastasio/firefox-privacy-restorer https://github.com/shawnanastasio/firefox-privacy-restorer

toastercat 5y ago

https://github.com/arkenfox/user.js https://github.com/arkenfox/user.js

johnisgood 5y ago
There is https://gist.github.com/MrYar/751e0e5f3f1430db7ec5a8c8aa237b72 https://gist.github.com/MrYar/751e0e5f3f1430db7ec5a8c8aa237b... as well (check out the comments, too). Or https://gist.github.com/davinian/1991bb3486cbf6005b5320e93b3f94d2 https://gist.github.com/davinian/1991bb3486cbf6005b5320e93b3... but it is quite old I think. In any case, make sure you know what you are disabling, because in the latter it suggests disabling WebSockets which you may not want to do.

Communitivity 5y ago

Supposedly this will opt you out: https://support.mozilla.org/en-US/kb/telemetry-clientid https://support.mozilla.org/en-US/kb/telemetry-clientid One way is to use your firewall to block anything going to mozilla.org or firefox.com, or the subdomains. That probably gets most of it, but possibly not all. For example, Google has a number of non-Google.com subdomains, some of which seem to be used only for telemetry. Another more involved way is to start WireShark or tcpdump and capture the traffic, then start Firefox and browse some, and then close Firefox and stop the capture. Now you have a list of all the traffic it tries to send, normal and telemetry. Sift out anything that looks suspicious and block the ip/domain via your firewall.

dveditz_ 5y ago

Or you just turn it off in the normal preference UI and trust that California's AG will sue Mozilla into oblivion if they weren't honoring the CCPA. https://blog.mozilla.org/netpolicy/2019/12/31/bringing-californias-privacy-law-to-all-firefox-users-in-2020/ https://blog.mozilla.org/netpolicy/2019/12/31/bringing-calif...