3 ms·
Actually, this is something that should be fixed in Privacy Badger. They can detect the URL parameter that flips ads from personalized to non-personalized (npa=
by d2wa 8y ago
Actually, this is something that should be fixed in Privacy Badger. They can detect the URL parameter that flips ads from personalized to non-personalized (npa=1) and block accordingly.
https://github.com/EFForg/privacybadger/issues/2046 https://github.com/EFForg/privacybadger/issues/2046
- phicoh 8y agoThat doesn't make any sense. The point of privacy badger is to prevent cookies that track you across different domains. Allowing tracking cookies just because a certain parameter is present is asking for abuse. If you are serious about not tracking people, don't use tracking cookies.
- d2wa 8y agoCookies is just a tool it all comes down to how you use it. Not all knifes are stabbing-people-to-death knifes.
- phicoh 8y agoPrivacy badger is quite specific in what it blocks. It blocks third party tracking cookies that track you across multiple domains. First party cookies are no problem. Third party cookies that are only used in one domain are no problem. Third party non-tracking cookies are no problem. So it does block the equivalent of bringing a large knife to a bar.
- opencl 8y ago"use cookies to combat fraud and rate-limiting (not showing the exact same ads repeatedly)" and "you cannot opt out of showing ads to users based on their previous interactions with the advertiser, such as visits to an advertiser's website, known as remarketing"[1] sure sound like tracking to me. Far less invasive tracking than Google normally does, but clearly still tracking. [1] https://support.google.com/adsense/answer/142293?hl=en https://support.google.com/adsense/answer/142293?hl=en
- fenwick67 8y agoPrivacy badger doesn't have filters like this. That's the whole point. It sees Google doesn't respect the DNT header (it sets tracking cookies) and shuts it down. This is privacy badger working as intended.