New
#30
500?? I've used Chrome for years and the most tracking cookies SAS has ever picked up was around 20 for a months usage. That's with the default cookie settings. 500 seems like a huge amount!
500?? I've used Chrome for years and the most tracking cookies SAS has ever picked up was around 20 for a months usage. That's with the default cookie settings. 500 seems like a huge amount!
I knew you were talking about Firefox LF, but what I meant was through all my years of using Chrome I've never had anywhere near that amount. Does Firefox handle cookies differently to Chrome somehow?
I prefer to use Chrome as I use a few Android devices and it syncs well with those. I'm tied into the Android ecosystem anyway, so I just have to go along with Google's excessive data collection, despite blocking and disabling as much as I can.
I haven't used Firefox since around 2010. I updated to a buggy version which caused me a lot of problems, so haven't used it since. I can't remember how it's set up by default, or how its cookie handling works. That just seems like an excessive amount of trackers.
That's one thing about newer versions of Chrome which annoys me. For some strange reason, when I choose the option to block third party cookies, I can't pay for anything online using a card. It gets to the authentication page and just times out. I've tried adding certain cookies to the allow list, but it never works. As soon as I allow third party cookies again I can purchase things.
Not sure what Google changed to cause this, but I have to accept third party cookies for it to work in the latest versions.
I get the same behaviour on Chrome for Android.
Firefox is pretty much the same (I tried Pale Moon a short while back—mayhap two months ago—and I was not impressed). I had it set to reject third party cookies but I just checked it and it had changed itself back to always accept them (mutter, mutter, mumble, mumble). The only reason I even have the POS on my computer is a recent IE11 update (September's) broke a handful of badly programmed websites (I'm blaming those websites, not the update, because the vast majority of the websites I visited since then had no problems from the update). I'm running SAS again to see if any new "infections" snuck in before reset the POS.
The SAS scan just finished and has 98 hits, every misbegotten one of them through equally misbegotten Firefox. Heck, I've hardly even used the POS since I last ran SAS. This a screen shot of some of them:
Hi,
I might add I also use in private browsing so not much of anything is saved even any cookies.
The problem with those settings is the desirable cookies also get deleted. It so simple IE to deal with. I have it set to ask before new cookie gets planted on my computer. I can either choose to allow it or not to allow it. I can also choose whether my choice applies thereafter or only this onetime. It's easy peasy with no hoops to jump through. Another bonus is I immediately know when a website is trying to plant cookies onto my computer.
Once upon a time, browsers like Firefox and its derivatives had that same option but have dropped it, probably because the developers got paid by the cookie planters (polite term: I would use more accurate terms but Mama told my not to use those words) to drop the option.
Hi,
You just add the wanted cookies in the exceptions field.
You can also block with exceptions too like when sas finds one or 500 hundred :)