21–30 of 59 posts
If this is added to the core (and simplified as mentioned by dotmanish), it can eradicate the chrome fever for good. The same reason why people are using DDG these days(btw, I do. for all my searches other than blockers while coding).
What looks to me as a counter-feature is that if I'm logged in to GMail, and want to stay logged-in, I have to whitelist the "google.com" cookies. Wouldn't that allow all the Adwords tracking cookies as well, across sites?
I wonder if a better (if probably impractical approach for in a plugin) approach would be to scope off-site cookies to the containing page's domain. So an ad network's cookies on facebook.com wouldn't be shared with them on google.com. This would eliminate a lot of the "follow you around the internet" privacy issues without forcing manual configuration.
I thought there was a big fuss about FF doing this by default or something.
If this is added to the core (and simplified as mentioned by dotmanish), it can eradicate the chrome fever for good. The same reason why people are using DDG these days(btw, I do. for all my searches other than blockers while coding).
People use Chrome because it's better than Firefox. Much better.
As I understand -- I'll have to sign in to every website I visit each time? (or manage white-list) Well, then it seems like a not a fit for me. But still, thanks for reminding that I can disable 3rd-party cookies -- I just did that for my firefox.
With Pingdom it asked me to reenter my timezone and site to monitor. It is like it totally lost my account without the cookie.
There's another nice cookie manager for Firefox called Cookie Monster: https://addons.mozilla.org/en-US/firefox/addon/cookie-monste... It allows you to maintain a white-list of sites that are allowed to set cookies and allows you to pick whether the cookies the site sets are persistent or discarded at the end of the current browser session.
...which is a built-in Firefox feature.
Clever idea... makes me wonder why no one came up with this in the past?
Here is how I am using this: 1. Install the add-on. 2. Panic that it has deleted all "not open now" websites' cookies. 3. Choose the option to "Suspend Operation" via the add-on icon. 4. Repeatedly "Undelete" all cookies until it's all done. 5. Keep the add-on suspended. 6. Now, for the next few days, I will browse like normal, but will remember to "whitelist" the websites I like to stay logged-in (Hacker News, Webma…
If this is added to the core (and simplified as mentioned by dotmanish), it can eradicate the chrome fever for good. The same reason why people are using DDG these days(btw, I do. for all my searches other than blockers while coding).
People use Chrome because it's better than Firefox. Much better.
Earlier quoted context omitted.
I wonder if a better (if probably impractical approach for in a plugin) approach would be to scope off-site cookies to the containing page's domain. So an ad network's cookies on facebook.com wouldn't be shared with them on google.com. This would eliminate a lot of the "follow you around the internet" privacy issues without forcing manual configuration.
So... Blocking third party cookies? I thought there was a big fuss about FF doing this by default or something.
- The privacy model of browsers relies on the same-origin policy. The same origin policy is in practice routinely circumvented by active identifier sharing. The difference between 1st party identifiers and 3rd party identifiers has become meaningless.
- Self-Destructing Cookies is a proof of concept for a model that actively derives the minimum set of identifiers that you need to browse the web at any given moment. This is a possible workaround for a world without the same-origin policy.
- Cache abuse is rampant. The cache must be considered a store of identifying tokens. If you use SDC, you should definitely enable the automatic cache cleaning. Set the timeout to 3 minutes or so. Remember that identifiers are frequently shared. It only takes a single party to identify you from something they put in your cache.