|User since||Aug. 7, 2010|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
Rated 4 out of 5 starsThis review is for a previous version of the add-on (188.8.131.52).
Rated 4 out of 5 starsThis review is for a previous version of the add-on (5.1.7). This user has a previous review of this add-on.
Rated 4 out of 5 starsThis review is for a previous version of the add-on (184.108.40.206).
Edit: 10/28/17 Review "Still not working in Tor Browser Rated 3 out of 5 stars
I felt obliged to edit part of my review from earlier on 10/28.
Re: uBlock Origin 1.14.16 and NoScript 5.1.2 / 5.1.3 now seem to work in Tor Browser.
It took several "removes" - uninstalls / reinstalls of NoScript before both addons worked in Tor Browser.
Finally had to remove most NS about:config or prefs.js entries left after uninstalling.
NoScript's remnant prefs "shouldn't" have bothered uBo, but apparently did.
That's the only thing different on the *LAST* uninstall / reinstall, when uBo and NoScript finally worked. No settings changes were made in either addon.
FWIW, NoScript and uBo did fine on my 2 machines, until the last few days. They both had updates in Oct '17, so one or both created an issue for the other.
Side: It's goofy not to be able to edit a recent review vs. forced to give another star rating.
1.14.16 STILL not working in Tor Browser 7.0.7 if NoScript is installed. Rated 4 out of 5 stars
The webext version isn't quite where the legacy was, but that's not totally the devs' fault. It's somewhat slower - not terribly. It's early.
uBo can be complicated. But default settings are usually enough. If something gets by it, it's quite easy to use the element picker. You can preview what effect the element(s) you just chose will have before adding the rule (that uBo writes).
In that regard, it's simpler to use than AdBlock Plus.
It still doesn't work in Tor Browser 7.0.7 if NoScript is installed.
As others said in uBo bug 3156, uBlock doesn't work properly with "Medium Security" in Tor browser 7.0.7. I imagine they were using NoScript (integral part of Tor Browser). With NoScript uninstalled (NOT possible, long term in TBB), uBo works with TBB security levels Low & Med, but not High.
uBo appears to be conflicting with NoScript.
The update to 1.14.16 didn't fix problem with NoScript.
Gorhill says in bug 3156,
" I test with *only* uBO, no other extension."
That's a mistake for TorBrowser. That's like saying for Firefox - "I didn't test it with OpenH264 codec installed," or any other critical component.
If you want to reproduce the bug / conflict, then NoScript 5.1.2 or 5.1.3 needs installing, as Tor Browser ALWAYS has NoScript - by default.
All the symptoms & problems described in bug 3156 still apply, if NoScript is installed. Even if it's "disabled," uBo didn't work. Had to temporarily uninstall NoScript to test.
"Don't file bug reports here" I'm sorry, tried MULTIPLE times to file "proper" bug w/ all required steps, details on Github - no go. I can post on any other Github project OK. Only so much time to devote. :)
v2.3.0 Too Inconsistent, right now. Rated 2 out of 5 stars
I know this is a tough time for Fx addon devs.
It will work OK on some text forms (say, some forum posts). When it works, it's easy to use. Needs more control over keeping or deleting entries.
But other sites, it may save only the 1st or last line typed. Other times, saves nothing - not even a blank entry.
At 1st, I thought it was uBlockO 1.14.4 interfering, but further testing ruled it out as the only problem. It was too inconsistent to show uBo was a problem or not.
I gave 2 stars because at least someone is trying to develop webext addons.
Curious-why open an addon in a new tab? Rated 3 out of 5 stars
Thanks for beginning a cookie manager for Fx 57+. I know it's brand new &amp; takes a lot of work. Just trying to give some useful suggestions.
1) Re: Taurean75's comment: https://addons.mozilla.org/en-US/firefox/addon/a-cookie-manager/reviews/896808/ - -
yes, I think they meant as in the link you posted: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/user_interface/Popups.
That's the way many addons provide menus, where options may require frequent changing.
2) If I understand, why have any addon open in a NEW TAB, instead of using a toolbar icon? Not a requirement for Fx 57 / webextensions? Or just the fastest way to get Cookie Manager up &amp; running?
Most Fx 57 ready addons I use allow adding icons with drop menus to toolbar. Few require using about:addons to *change* (most) options - especially for cookies.
3) Suggestion: post a few more screenshots on MAO w/ some explanations. Probably entice more users to try it. I see Cookie Monster's dev has pulled it from AMO. Lots of users will be looking for replacement.
Keep up the good work. For ideas, I'd look at features in the more popular cookie managers - that aren't updating to webextensions.
If you want feedback of what's most important to users to implement 1st, maybe setup a support page on http://forums.mozillazine.org, as other addon devs did. One post could be a poll for wish list.
I could tell you some cookie features I've used most - for years, &amp; read others say were important to them, but it'd make this review long(er). Maybe you don't need ideas for now. :) But, feel free to PM me.
Edited review 08/13/2017: correct typos
addon works fine Rated 5 out of 5 stars
I've used the addon a long time - works fine.
@ tidrug - you mentioned posting steps how to create and use keywords, to specify using a particular search engine for searches from the address bar.
People might appreciate that in light of talk about Mozilla possibly removing the search bar & entire "search box" in future Firefox.
parsing error sitecookies.xul Rated 4 out of 5 stars
Re: a previous reviewer's comment & dev's reply - " Thanks for the Notification
by s1tony (Developer) on April 28, 2017"
I believe there's a syntax error on line 35 of sitecookies.xul. This would be easy to fix.
Whether that is the only problem, don't know.
I can modify the file, but that changes the checksum, invalidating the extension signature.
I'm not sure if methods to override extensions signing requirement (there were a couple) still work in Fx 53. At the moment, don't have time to test methods if Fx 53would install modified extensions.
Thunderbird 52.1.1_Linux started blocking SmilieInserter images Rated 4 out of 5 stars
Seems like SI+ v1.11 worked in Linux Tbird 45 & worked well in Vista;
starting in Linux Tb 52, when try to add a SI Plus image using its drop menu, Tb pops a blocked image message at the bottom of composer window.
That message has a preferences button, that would allow unblocking (apparently) only the *specific* smilie file selected. Guessing a new Tb security feature?
But, Tb 52 allows me to drag / drop an SI Plus file directly from its folder (Linux) to the compose window. That doesn't make a lot of sense, since by either method, the location of the file being added is the same.
Works on some? sites; few users know how to write plugins Rated 3 out of 5 stars
If the goal is to download from the few sites with included plugins in DTA-anticontainer, it may work. Except sites change their coding constantly. Plugins will need updating - as several reviews mention & support site requests.
If a site doesn't have an included plugin & DTA (by itself) or with DTA-AC still does what you need - great. If not, most users probably won't know how to write plugins that actually work. One reason - scripts & page source for different sites vary a lot.
There is a "tutorial" on writing plugins on the support page - wiki, but examples don't show what data from a site's source was used, or why - to decide what was needed for the plugin. The example plugins just sort of appear - there is some explanation. Not enough for most "technically inclined" users to write their own.
The addon needs detailed examples & step by step instructions - how to look at sites' source code (on sites, R click a page > View Page Source) and explain - based on the page's code - how to decide what's needed in a plugin.
My guess is, users with some knowledge could spend hours writing & troubleshooting one plugin.
The instructions on replacing updated plugins (that aren't yet in official releases) are insufficient for average users to follow. https://github.com/downthemall/anticontainer - Under "Pro Tips" at the page bottom.
Developing an * almost * automatic "wizard" to create plugins would be a lot of work. For typical or moderately advanced users, without step by step instructions on writing plugins based on sites' actual source code, this addon may have limited use.
* They do not collect or allow to be collected, data that's personally identifiable in any way; including but not limited to browser profiling data that could be used to identify users in any way.
* What types of data they collect, if any, and exactly what they do with it, how long it's retained, etc.
It's strange Mozilla doesn't seem to require addon privacy policies.
Without one or a poorly written one - for any software, devs can do pretty much what they want. There have been several publicized cases where addons were collecting personally identifiable info (not just Firefox addons).
Mozilla should also require privacy policies for plugins, written so average users can understand.
Still in infancy_many bugs & odd behavior Rated 2 out of 5 stars
Lightbeam 1.1.0 in Windows.
As of v1.1.0, I wouldn't place complete confidence in what Lightbeam is showing.
Yeah, it's kind of neat, but if you read its bug reports, there are too many quirks.
Many buttons, scroll bars, etc., have bugs - at least in Firefox 34 (reported by many users).
I have not found any kind of user manual or "how to use Lightbeam" instructions . Without them, interpreting some of the data is questionable.
One thing I notice is, how much effect the setting for "network.http.sendRefererHeader" (in about:config) has on Lightbeam results. That setting affects whether it shows any of the sites on the graph as connected - with lines, or not. I assume the lines connecting the circle or triangle sites on the graph shows if they're actively tracking you between sites?
If I disable sending of any referrer header info (in "network.http.sendRefererHeader") by setting = 0, none of the sites shown in Lightbeam graph ever show connecting lines.
If sending of referrer headers is allowed (default in firefox), and if no other addons are blocking any tracking, etc., then Lightbeam shows lots of triangle &amp; circle (sites) connected.
! There's a reason concerned users have blocked sending referrer headers, for a long time!
NOTE: concerning results in following paragraph(s) & addons listed, I also tested Lightbeam 1.1.0 in a * clean * profile in Fx 34. Most Lightbeam bugs & oddities persisted in the clean profile w/ no other addons & no changes in default Fx prefs.
I also don't understand the meaning of some data Lightbeam shows ( no manual or detailed wiki).
For instance, even w/ these addons fully blocking all trackers: AdBlock Plus, Ghostery, NoScript (w/ ALL scripts blocked); and all session / 3rd party cookies BLOCKED, and no referrer headers allowed, Lightbeam still shows at the TOP of List view, "You have connected with 5 Third Party Sites."
At the same time, in the actual list of sites (in list view), in the column "Sites Connected," all values are zero, for 3rd party sites &amp; for "visited" sites. Even for visited sites w/ tabs still open, it shows a zero under "Sites Connected."
Also at the same time it says I've "connected to 5 third party sites," the graph usually doesn't show any 3rd party sites. How to interpret the several discrepancies? Who knows - can't find instructions.
With all my blocking addons &amp; other settings, it's very unlikely that I've connected to any of the 3rd party sites that Lightbeam shows in its List view.
Add details on what is cleared & provide support in English? Rated 3 out of 5 stars
Could you add more details in the description of exactly which cache(s) it clears? "Cache" in modern browsers means more than one thing.
Instead of users installing, just to find out very basic features.
I also d/l the xpi file, unzipped & looked for readme / features file - don't see one. I thought you mentioned to a reviewer that you'd include more info "in next version" - which I though was before the current of 1.4.
Went to your support page - only in Spanish. No button / flag on the page to switch to English. Would be really helpful, so users / potential users don't have to leave questions here on the "review" site.
Sorry for the '3' rating. When I get info & do an actual review, I'll change this if possible or do another.
Still working Rated 4 out of 5 stars
Used CM for a long time. Now on Fx 28. Still no problems.
"The only issue I have is every time I run CCleaner I lose the preferences for what sites are Allowed/Denied/Session."
That's not a Cookie Monster issue. It's the CCleaner preference to clean "site preferences" for Firefox - possibly other browsers. Uncheck that for Fx, Tbird, )other browsers?).
Site preferences are the same as exceptions (regarding cookies). The same thing would happen to anyone that checked to have Fx clean preferences at shut down, under Options > Privacy.
Comment by AMO admin on users' & / or devs' conversations in Reviews Rated 1 out of 5 stars
This is not a review. Do not attempt to adjust your monitor.
I suggest another method be provided ASAP for users to communicate w/ the dev & vice versa, separate from *reviews.* For one, if users need to ask follow up questions / give replies to devs, the review system requires users to create a new review each time.
They can't just enter follow up comments / questions. One important issue with the current Textarea Cache user - dev contact process is, creating subsequent reviews *only for back & forth dialogue* will skew the addon rating. It's also hard for other users to follow the conversations & benefit from the dialogue.
Some AMO extension devs use one continuous Mozillazine forum thread for their support "forum." It's not the best, for searching the forum for topics, but it's better than using the review area.
AMO admin points out the review system was *never intended* for conversations between users & devs or for support:
"Reviews weren't designed to be for conversation. Developers should provide *contact information* so you can discuss any issues with the add-on. Reviews should be limited to rate how the add-on works and we only provide developer replies so they can tell users where to get additional help or continue the discussion."
- jorge-villalobos AMO Administrator
Good but very complicated for avg to lower-advanced users Rated 3 out of 5 stars
I've used NoScript off / on for couple yrs; full time for several recent months, where I've actively read online "help file" (really, just description of features), combed thru old NS forum posts, searched online for posts / articles relating to issues I had, posted questions on the NS forum.
If that sounds like a lot of time - it is. If you're NOT a web programmer or a *serious* (good) techie, you may need a lot of help &amp;amp; guidance for NS on some sites. (before saying, this is just a person w/ no clue of apps, extensions, computers... look over my background, farther down.)
Part of the reason you may need hands on help is, there's really no help file, per se. For what may be *the* most complicated Fx extension, not having a full-blown, detailed, step by step Help file is a little like driving a space ship you came across, w/o a manual. :D
I like the concept of NS. I think it's protection is important.... Yes, it works OK much of the time. BUT...for sites it doesn't (even some big, name brand ones), depending on your patience level, it may drive you to the brink. Don't believe it? Browse the forum. And it's not just users that have no clue about anything.
I think the "avg NoScript user" is anything BUT an avg *computer* user. Avg NS users are likely extremely advanced users who: 1) at times, can sort thru mounds of technical data, incl. code of the websites, looking for solution to why a site doesn't work, and 2) don't mind spending a LOT of time doing that (at certain times), to keep using NS &amp;amp; get the protection. Almost a labor of love &amp;amp; ** I sort of fall into the last group.** :)
I'm far from a coder / pro. IT person, but I regularly edit &amp;amp; fix things in all SORTS of apps - &amp;amp; not just in simple text files. I regularly find solutions to problems that even the devs of apps, extensions can't &amp;amp; have been at it for 15 - 20 yrs. I've an engineering background, can build / completely disassemble &amp;amp; repair computers (or cars &amp;amp; engines, or all major appliances, electronics).
But that's not enough to solve all NS issues (when they appear - & they will), because I'm not a programmer or web developer. In part, because how certain aspects of NS work (in detail) isn't documented. Sometimes if it is, there's only enough details to make you dangerous.
I will say, if you leave all java scripts enabled, NS still has other very worth while protection. Those aren't 100% "trouble free," but far less so than troubleshooting NS issues involving blocking certain scripts.
Reply to Hemiola SUN's comment to Joebt Rated 3 out of 5 stars
Reply to Hemiola SUN's (dev) reply to Joebt:
Thanks. I think adding an option to "clear cache I close Fx" is in order. But you could poll users on it. If it's something a fair number of users want, at least sometimes, probably shouldn't make them alter about:config.
For one, avg users may not be comfortable making about:config changes; don't know how, afraid of the unknown, etc. 2) settings that "are out of sight, are out of mind." It's hard to remember changed settings that don't appear in apps' UI.
If for any extension, users are expected to modify about:config, the info for specific changes should be widely, prominently available: FAQs, User Guide, etc.
I also notice if you UNcheck option, "Keep data in the cache when I start Fx...", then ONE of the 2 sub-options under it remains checked & "active." If that main option is disabled, shouldn't its sub-options be disabled? Or do those sub-options actually remain active when "Keep data in the cache when I start Fx..." is UNchecked?
I highly suggest adding menu options under "Keep old data in the cache for": 15 min, 30 min, 1 hr. Users don't necessarily want options now available under "clear cache I close Fx." If not, then during same session - under "Keep old data in the cache for", they likely may not want / need to keep cache an entire day. One reason - it's hard to determine when the "Day" will expire at "One Day."
"Clear Cache Now" option on main menu is almost a necessity. It would improve useability tremendously.
It Works; Explanation of new version changes? Rated 4 out of 5 stars
Been using TAC for couple months. So far, so good. No real complaints. I've had to copy text from TAC a couple times & it worked.
1) At 1st, some may miss that when the UI holding * actual * saved text is opened, there's a drop button on the header. By default, it shows the date & name of most recent site where text was saved; the drop button in that box will show all saved "text sessions" that can be selected (that part's good).
2) What I don't understand is why there's no option for time to save cached text, like:
"keep until I [b]CLOSE[/b] Firefox," or
"keep for 'X' hours".
Currently, the 1st option requires keeping stored cache after Fx closes: "Keep old data in the cache when I start Firefox Next Time,"
then... choose secondary option - either:
"then remove them 5 min later.
"then remove when I close Fx again."
2-a) I guess this is for times Fx crashes / locks up & text cache can be saved at least until it's restarted?
Drawback is, that DOES save text after you close Fx - if that's a privacy concern. Some don't want to keep the cache after they close Fx.
2-b) I suggest adding options: "Delete cache when I close Fx."
and, "Delete cache after X hours" (either several time options or enter a value).
Not everyone needs it to save cached data for a full day, either.
3) If it's going to save the cache until Fx is restarted, there should be a menu option added (right from main Addon / Navigation bar icon) - to "Clear the cache NOW." So, if something private was typed / saved, and you're closing Fx normally, you don't have to go several layers in, to clear the cache - if needs clearing immediately.
I'm aware that we don't usually ask questions / get support on the MAO site, but there's no OTHER form of contact. Except to report bugs.
4) When new version changes are made, could you add a tiny bit of explanation.
What exactly does " * Remove status icon" mean? Which "status" - the pop up status bar?
I wasn't aware of a status icon. If "display status bar icon when texts are saved..." is checked, it displays an addon bar icon. It will also allow putting an icon on navigation bar (bar usually at top, R).
You're not talking about the addon bar?
Seems to work_can't remove toolbar icon Rated 4 out of 5 stars
Haven't used it extensively - esp. in Fx 23. Basic sorting seems to work.
Don't use some of more advanced features - yet.
DEFINITELY need to fix so can remove the icon from addon bar. Can drag it away to the "icon stash" box, during customize, but next Fx restart, icon is back in addon bar.
Descriptions of settings in the options UI are helpful.