Bewertet mit 4 von 5 Sternen

I love this plugin, but I'm beginning to notice that some sites are still tracking me using other techniques. A good rundown of the really long list of ways you're being tracked can be seen in the description of evercookie: . Unfortunately, plain HTTP cookies are just the tip of the iceberg now, and I haven't found a (non-sketchy) way to defeat everything listed here. Would be great if SDC wanted to take on this much larger issue.

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Agreed, although many of the techniques in that list can already be defended against. The major remaining problems as far as I can see are LocalStorage and the Cache (this one subsumes many of the individual bullet points). I already have some code in the development branch to deal with LocalStorage. Unfortunately, the API that Firefox offers is nowhere near as comprehensive as the one for cookies. I'm still evaluating the available options. Stay tuned.

Bewertet mit 5 von 5 Sternen

I've installed this, really targeting a handful of domains from just one particular site, but the author is right, when you see it clearing out all those other ad cookies too, you don't miss them either. But the behavior of it working immediately, automatically, and fully is a problem.

Here's what I would do. Since the app pops up a growl notification as it removes all these cookies (I'm on OSX, do other OS'es get similar notifications?), have the plugin work in "dry run" mode when first installed - reports on what it would be removing, but doesn't actually do it just yet. This way, you can browse around and click the "greenlight" button at the bottom for the sites you care about to whitelist them. The notifications will tell you "disable dry run when you're ready", which you do in the plugin preferences (also there should be some behavior in the icon that allows you to open the pref window quickly without going through tools->addons->.. .unless there is and I'm not seeing it).

Another issue, the plugin boasts that it doesn't need a restart, which is true. *But*, I had no idea about the "greenlight" button in the toolbar, which is awesome, until I happened to restart at some point, and I really wish I knew about that button immediately, so if the plugin needs a restart for that to happen I'd say do a restart.

Another feature that would serve my original use case, but I suspect not the author's, would be an optional "blacklist" mode, so that one can work in the other direction. I know that's not the spirit of the plugin but I'd be interested in experimenting with that mode, even though I'll probably stick with the "whitelist" mode since its easy enough to add the twenty sites I genuinely want to preserve cookies on.

The author appears to be responding to comments here which is worth a star of its own and the plugin is very smoothly implemented, so I give it five.

PS, also wanted to ask does Firefox Sync pick up the whitelist and other settings for this? Not sure if things are capable of working that way.

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Thank you for your suggestions. Improving user-friendliness is the big theme for the next version.

I had pondered your idea to improve the first-run experience before. I fear that I'll get many angry mails complaining that my add-on does not work if I start it in a paused state. Here's what I came up with instead: the current beta-version already has a pause-and-undelete function. It's just not enabled by default because I want the user to be aware of the security implications. I think I'll just temporarily enable it the first time the add-on is run and open a tab with instructions on how to recover the cookies.

I'll also advertise the toolbar button more aggressively once that version is out. It had already gained some new functionality in the development branch so I postponed taking screenshots of it.

I see the appeal of a blacklist mode for "that" site. It might happen one day.

Regarding Firefox Sync: good question, I had never considered that although I use this feature. SDC uses Firefox's standard site permission database (it also stores popup and plugin permissions among other things). It seems that this is not included when syncing. If Firefox one day includes site permission in its sync, SDCs whitelist will also sync automatically.