5 ms·
> ... you don't need to worry that toggle will get mysteriously turn back on. Using Firefox Developer edition and toggle(s) will get mysteriously turned back o
by dig1 3y ago
> ... you don't need to worry that toggle will get mysteriously turn back on.
Using Firefox Developer edition and toggle(s) will get mysteriously turned back on all the time. And Mozilla is not immune to this practice at all for standard Firefox.
Use chromium-ungoogled [1] if you want chrome(ium) without Google-specific stuff.
[1] https://github.com/ungoogled-software/ungoogled-chromium https://github.com/ungoogled-software/ungoogled-chromium
- tga_d 3y agoUsing these sort of downstream patch set browsers is rarely a good idea. If it has multiple full-time developers from a respected org dedicated to it, then it can be justifiable (Tor Browser, Brave), but take a look at the gaps in time for these two pages: https://github.com/ungoogled-software/ungoogled-chromium/releases https://github.com/ungoogled-software/ungoogled-chromium/rel... https://metadata.ftp-master.debian.org/changelogs//main/c/chromium/ https://metadata.ftp-master.debian.org/changelogs//main/c/ch... There's often days you're going without security patches. If you want a browser without Google tracking, Firefox is a much better choice.
- pffvgvp2 3y agoI don't understand why someone hasn't just setup an automated build system that patches out google/previously-unseen URLs in each new chromium release, and posts builds. That's all you really need to disable telemetry, surely?