|User since||December 19, 2007|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
Important Add-On Rated 5 out of 5 stars
Collects all preferences related to privacy and security. I wish firefox would offer such a compilation in its Preferences / Privacy section, e.g., as "Advanced Settings". Very convenient: For each preference, this add-on provides information on its meaning, partially complemented by web links. I agree with some reviewers that an import/export facility and switchable profiles would be nice. As a not so handy substitute, I currently fiddle with prefs.js (comprising _all_ firefox preferences) in the profile directory when I have to check why a certain website no longer works.
Thanks a lot!
Really Great! Rated 5 out of 5 stars
I find the concomitant reloading of the web page upon whitelisting, i. e., upon turning JS on, very convenient.
During the last few weeks of heavy use, I encountered only two problems with this add-on:
The login page https://abc.xyz of my email provider certainly needs JS, hence I whitelist this page leading to the entry "abc.xyz" in the whitelist. After typing in my credentials and hitting the login button, the web site directs me to the page "https://navigator.abc.xyz". For this web page, however, JS is deactivated, in spite of the entry "abc.xyz". This is detected by the web site and it returns immediately to the login page, presenting empty fields for my credentials. (No chance to interrupt that process, no error messages, I cannot see the page "https://navigator.abc.xyz".)
To circumvent this problem, I have to disable the add-on via the about:addons page of firefox and log into the web site. Then I re-enable JS whitelisting and whitelist "https://navigator.abc.xyz". (Fortunately, the provider always uses the same address instead of navigator1.abc.xyz, navigator2.abc.xyz, etc.)
To remedy this inconvenient situation, I suggest to provide an easy way for disabling the add-on. For instance, if I left-klick on the button of the Flash Control add-on, a short menu with three entries pops up: (1) allow/disallow flash at the current page, (2) disable/enable Flash Control, (3) open preferences. In addition, entries like "abc.xyz" or (better) "*.abc.xyz" in the whitelist should match any subdomain of "abc.xyz". Finally, a direct way of adding entries to the whitelist would be helpful.
Since the add-on does not provide a direct way to add entries to its whitelist, one has to resort to the add-on's export/import functions. Once a file has been loaded, however, the add-on remembers its name and (silently) refuses to load it again, even if it contents changed after the last import. It's only after renaming the file and selecting it in the preferences that the add-on is willing to import its contents again.
Thank you for this important add-on!
Very Nice! Rated 5 out of 5 stars
By the help of this add-on I was able to group all firefox windows as one block in the window list of my window manager (title pattern "[firefox]t"). Before this, the title of the active tab was the leading part of the window title, leading to scattered entries of the firefox windows in the window list. (This list is sorted alphabetically.) THANX!This review is for a previous version of the add-on (0.5.5-1.1-signed.1-signed.1-signed).
Nice Little Helper Rated 5 out of 5 stars
CookieCuller is the only tool I know of that allows for managing individual cookies. Most cookie management tools provide only rules based on server addresses. In certain situations, a more fine-grained control is desired.
I agree to the criticism of some of the reviewers regarding the user interface. In the beginning, one must experiment a bit in order to establish the correct interplay between the cookie management of firefox and CookieCuller: I usually switch off all cookie deleting done by firefox and switch on 'Delete Unprotected Cookies on Startup' in Tools -> Add-ons -> CookieCuller -> Preferences. It would be very helpful if this important option could be moved to Tools -> CookieCuller. To avoid an unintentional loss of cookies in the beginning I suggest to shut down firefox and to make a backup copy of the file cookies.sqlite in one's firefox profile directory.
Another con is that CookieCuller deletes unwanted cookies only at the next start of firefox instead of deleting them at shut down.
Bottom line: Thanx for making available this nice little helper!
Thanx! Rated 5 out of 5 stars
Until today, I used CookieCuller to keep a single cookie when starting firefox: This was google's PREF cookie that contains the google search preferences amongst other things. Only recently I became aware that among these 'other things' there is a unique ID making possible the correlation of google searches across many sessions.To change that ID but to keep the cookie with its preferences I tried several approaches: (1) I wrote a greasemonkey script. This worked out but needed a bit of tinkering. (2) I manipulated cookies.sqlite via a script. However, this could only be done when firefox is not running. (Firefox locks the db file.) (3) I installed OptimizeGoogle which was the easiest and most powerful solution.Currently, I use the sticky preferences of OptimizeGoogle (only session cookies permitted). As a consequence, one has to change the google search preferences within the preferences of OptimizeGoogle instead at google's search settings page. If further testing reveals any problems with this approach, I will revert to the solution based on a permanent google PREF cookie, in which case the UID anonymizing feature of OptimizeGoogle will still prevent google from correlating searches. So far my tests are very limited (opensuse 11.1 + firefox 3.6.12, test duration = several days, only google search preferences and UID anonymizing switched on), but until now OptimizeGoogle works nicely!Bottom line: Finding a good balance between privacy and convenience is a tricky business. Tools like OptimizeGoogle play an important role by helping the non-expert to gain more convenience without sacrificing privacy. To support maintenance and further development I just made a small donation via the project's home page (my first one for a mozilla add-on). Thanx!This review is for a previous version of the add-on (0.78.1).