[PrivacyBadger] deleting existing tracking cookies

Cooper Quintin cooperq at eff.org
Thu Jun 25 11:43:41 PDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think this is an interesting idea. An open question here is how to
decide which cookies to throw out. For example, we could obviously
throw out doubleclick.net cookies with little concern as to the effect
on the user's browsing experience. Unfortunately the same cannot be
said about google's cookies, or other cookies which serve as both
first party and third party identifiers. If we were to throw out
google or facebook's cookies when those domains become blocked it
would have the undesirable effect of logging people out of their
accounts, which could cause frustration and confusion. One possible
solution for this would be to only throw out cookies for domains that
become completely blocked—this would require a lot of testing though,
as I still fear it would cause a lot of unexpected breakage.

- - Cooper

On 05/30/2015 07:41 AM, Brian J. Murrell wrote:
> Not sure if this is OT here or not.  It seems at least
> tangentially related... but I wonder if there is any possibility of
> Privacy Badger deleting existing tracking cookies.  Or maybe there
> is a different tool for that already?
> 
> It's all fine and good that Privacy Badger blocks new tracking
> cookies from being set but what about the cache of cookies that
> might already exist in one's browser?  One solution is of course to
> just clear all cookies but that's throwing a lot of baby out with
> the bathwater in that there is a lot of useful non-tracking data in
> cookies.
> 
> Thoughts, ideas?
> 
> Cheers, b.
> 
> 
> 
> _______________________________________________ PrivacyBadger
> mailing list PrivacyBadger at eff.org 
> https://lists.eff.org/mailman/listinfo/privacybadger
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJVjEvdAAoJENDqe2/wr+LKTDsP/A5K8u6/kyf2i/iQzO91/T/0
hkEYf9mUcSSbhoad2O2kSk7q1HcvwjpRDhkKVXlmJMJ25GF3QjnJjRV/uKrSATXS
dtyo1z2Mgh+bigsg4ezXUNApuN82SeqoBrow1VghjPy6kWiDXdW3goCgIIYzN/k0
ZzIO3eYzNPS9UMehnt8OhkWvsmv31xrluFajD7cVyOcpBzlXfV6DvkZRDzkYqyxz
hzczGqudm9W0qbxWiM0KFvPfYkOM91ZWO2i56QOhp8FxA/8yYXVEslzqm4zIqrmz
MeokUBowuu7diKukfytsqqlt3BVcA7KJXT8GJrRjFuOs9YSlz8xd7EQKLw5zSTNx
esMp3XEkjm78xDnlSOt2hWJDRpVhte2AV1BAVLOLzKhMfhzJFpNvY+IynBUN0d/A
ghZ85VD4bmMDuFxzjVOiVrGCIiq6YnNqqZoCPI6OanQrh06pWBNL0Katdo01EMvC
x1sTCcpn2TqXIac6lmfnLJenViXX++b1JDmjKOTcqzNzIz0otTTgaMnWBb5+qrQn
IeqAMzJW2Nv1SroKxiMo19tCqbeJgnESkz6UL+USz9Hhf/7utEK0XwSZrDfxlg03
Qnab2Ry22bosGS7oroDWzgNQmZPS5B3zNvSfvE1IyBH5a8BLSVurw5ScYRtPuCy4
XiLWFBdN4bPwExM3RsDk
=q9sZ
-----END PGP SIGNATURE-----


More information about the PrivacyBadger mailing list