31–40 of 43 posts
you can keep a whitelist of allowed permament/session/temporary cookies with https://addons.mozilla.org/en-US/firefox/addon/cslite-mod/
1. https://addons.mozilla.org/en-US/firefox/addon/self-destruct...
you can keep a whitelist of allowed permament/session/temporary cookies with https://addons.mozilla.org/en-US/firefox/addon/cslite-mod/
That sounds similar to Self-Destructing Cookies[1], which I'm using. Has anyone tried both and can compare them? 1. https://addons.mozilla.org/en-US/firefox/addon/self-destruct...
Same with Vanilla cookie manager on Chrome, except I don't think it deletes localstorage, flash cookies, etc because of limitations of Chrome's api for extensions. I think the attitude with Chrome is that you're supposed to use Incognito windows for this purpose.
Earlier quoted context omitted.
In my opinion it is actually pretty scary. As I see it, a website should upon landing either set zero or one cookie, depending on if the website has some sort of persistent functionality (like a message to first time visitors). The other 43 cookies are, in my view, therefore unnecessary to the normal functioning of the website, and is therefore more likely being used for other purposes such as tracking and advertisin…
Sadly I think that a lot of businesses either don't care or don't think about the cookies and tracking added to their site. In my experience it's usually the marketing department that want much, not all, of the things that end up setting cookies. It's not that it's a bad idea necessarily, but it's adding tracking upon tracking upon tracking and rarely a request to remove something. Some sales person try to sell marke…
Earlier quoted context omitted.
It's running a headless browser with JS enabled so it should be there... not sure why it doesn't pick it up. Thanks for the mention :-)
If you are running PhantomJs, did you encounter any issues like memory leaks and socket errors ? I'd be interested in the solutions you used to solve issues like that if it's not proprietary / private.
Evil ad networks only need a handful of cookies to track you. They could probably go without cookies entirely, just by fingerprinting the browser. They have the resources and know-how. This happens because many webmasters build frankensites by copying and pasting snippets of code to get the functionality they need. Those load a bunch of resources from all over the net and dump a jar of cookies in your lap. It's the s…
you can keep a whitelist of allowed permament/session/temporary cookies with https://addons.mozilla.org/en-US/firefox/addon/cslite-mod/
This article is completely incompetent. Firstly - any number of cookies from a single domain are equivalent, you can always use whatever identifier is in the cookie's data to store and retrieve an arbitrary amount of data about the user. That there are lots of them implies either that the site is using a bunch of different front end libraries / components that don't talk to one another (which is irrelevant from a pri…
>> opposite of a privacy issue, since it's keeping your data in your browser. In a way instantly accessible to the host site. Data I wasn't really consulted about. Data I might not be comfortable sharing every time you ask for it. This whole law about disclosing cookie use, which I will agree is not necessarily a good approach to the problem, does nevertheless exist because of a problem - People getting tracked, foll…
Earlier quoted context omitted.
If you are running PhantomJs, did you encounter any issues like memory leaks and socket errors ? I'd be interested in the solutions you used to solve issues like that if it's not proprietary / private.
Also interested, I've tried similar things with watir webdriver and a xvfb/headless mode but the only real 'solutions' I've come across are time-outs. Needless to say it could've been heaps better.
Earlier quoted context omitted.
>> opposite of a privacy issue, since it's keeping your data in your browser. In a way instantly accessible to the host site. Data I wasn't really consulted about. Data I might not be comfortable sharing every time you ask for it. This whole law about disclosing cookie use, which I will agree is not necessarily a good approach to the problem, does nevertheless exist because of a problem - People getting tracked, foll…
As a website owner I'm free to respond with any HTTP headers I feel like like when your computer makes a request. You're free to use a browser that doesn't decide to store cookies when you get a reply with those headers.
Not really very much. Particularly in the mobile space.
I never understood why cookies receive so much attention in various privacy discussions. They are the one thing the user has full control over. Yes it takes some effort to delete them, but so does looking left and right before crossing the street.
We've got into a situation where the vast majority of users don't know and don't want to know about any of the details of what's going on, and by default most browsers just allow them to be tracked in a variety of different ways. Website writers/maintainers quite often don't know themselves what a framework is doing, and everyone writes using the assumption that cookies are something they can just use. It sometimes looks like everyone except the end user was involved in the development of the situation.