Major Browsers to Prevent Disabling of Click Tracking Privacy Risk (BleepingComputer)
Major Browsers to Prevent Disabling of Click Tracking Privacy Risk (BleepingComputer)
Posted Apr 21, 2019 15:51 UTC (Sun) by oldtomas (guest, #72579)In reply to: Major Browsers to Prevent Disabling of Click Tracking Privacy Risk (BleepingComputer) by mathstuf
Parent article: Major Browsers to Prevent Disabling of Click Tracking Privacy Risk (BleepingComputer)
Firefox. My main profile has javascript disabled (don't ask). For good measure, my /etc/hosts contains "things" (yes, I'll go berserk again when browsers start doing "DNS requests" via HTTP).
Sure, the measure is extreme, and perhaps Ghostery might fare better, perhaps not.
Many sites which I'm interested in still work (LWN is one of them). When something doesn't work... I consider whether it's worth to me to use some more permissive profile: most of the time it just isn't.
My beef with Mozilla is that it makes those choices more and more difficult -- e.g. making disappear this easy choice ("turn off Javascript) in the UI precludes more timid users from even experimenting with it... with the (umm...) justification that those users are Just Too Stupid to switch it on again (just an example).
> Remember, the real culprit here is Google [...]
Don't get me wrong: Google, for me, is in quite another category. I said I want to love Mozilla. I definitely don't want to love Google.
Posted Apr 22, 2019 15:52 UTC (Mon)
by foom (subscriber, #14868)
[Link]
You could look into "proxy autoconfig" (PAC) files. This mechanism allows you to write a simple JavaScript function to tell the browser how to access a given hostname (e.g. directly to the host, through an http proxy of your choice, etc). You can configure the browser to read it off a file on your machine, or via http. Every browser supports this, as it's commonly used in corporate situations.
Major Browsers to Prevent Disabling of Click Tracking Privacy Risk (BleepingComputer)