Add extra features and styles to make SeaMonkey your own.Close
|User since||November 12, 2007|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
If one simultaneously runs Firefox with Lazarus and Chrome with Lazarus, there is apt to be an extraordinary amount of disc thrashing, and both browsers will do a lot of locking-up.
Wips, the reason that people think that your software installed itself is because, with your update, you didn't announce things properly.
Your page should have said “We've updated BlockSite. As part of the update, we've added the OPTION of some data-gathering. Now is your chance to OPT-IN. If you don't opt-in, you'll still get the functionality that the addon has been providing. If you do opt-in, then ….” And the opt-in button should have been the SECOND and SMALLER button.
Instead, the page didn't say what was installed that was asking permissions, and it started throwing up little messages about other sites. I had to launch a different browser to safely investigate what the H_ll had happened.
And I'd bet dollars to doughnuts that you don't understand that you had an _ethical_ obligation to think more carefully here.
You don't deserve another chance in this matter.
derek notes above that this addon leaves stuff in the configuration file even after it has been disinstalled. Users can open the configuration file by entering “about:config” (no quotation marks!) in the URL field. If you search for “wips”, you'll these Preference parameters:
plus an innocent
Right-click on each extensions.wips entry and select “Reset”. After you close the config file, those entries will be completely removed. (Leave the innocent font preference alone.)
When I launched my browser to-day, I suddenly found myself being asked to grant something — a deliberately unidentified something — permissions that I didn't want it to have. Investigation revealed that the something was this addon, which has been modified to become user-monitoring software. Naturally, I've uninstalled it, and wish nothing but horror upon the persons responsible and upon their living ancestors.
Do NOT try to force visitors to your website to use an HTTPS connection. I'm definitely uninstalling your software, because you are plainly not to be trusted.This review is for a previous version of the add-on (0.7.0). This user has a previous review of this add-on.
As others are noting, with Firefox 22, SkipScreen causes a plague of dialog box with the message “SkipScreen cmp: Error: Illegal operation on WrappedNative prototype object.” Now, any sort of plugin can develop a compatibility problem as the principal app evolves, but Mozilla plugins contain a declaration of the versions with which they are compatible. The declaration for SkipScreen 0.7.0 seems to have been falsified.This review is for a previous version of the add-on (0.7.0).
With this add-on installed, Firefox on my system (64-bit Fedora Core 17) generally failed to download .PDFs at all. (It would open-up a blank tab, but that was a rather poor susbtitute.)
Until fairly recently, FireFTP has worked pretty well for me. But, with the move to Firefox 6.x, the listing of FireFTP has disappeared from my Tools Menu. Searching the Web, I see that such disappearances did not begin with version 6; they've been happening to users for years. What I've not found is anything on the FAQ about how to fix the problem. That silence is itself a documentation bug, evidently persistent.
I guess that I'll shift to stand-alone FTP utilities.
I'm very glad to see that the developer has provided a new version of this add-on, compatible now with Firefox 4.0!
The bug in Firefox itself which this add-on patches would otherwise bite me with pretty much every session.
Firefox 4.0 continues the passive-aggression of earlier versions; and thus there is, as wonderboy76 has said, a real need for a version of this add-on that will work with FF 4.0This review is for a previous version of the add-on (1.3). This user has other reviews of this add-on.
During active development, this add-on could prove invaluable to a developer. But, for a user seeking to identify which-if-any piece of installed software is causing problems, this plug-in would better confine itself to a single logging window, and never never never seize focus. Instead of grabbing focus, it could have an audible alarm and a flashing iconette. And it would still serve those aforementioned active developers were its interface thus changed.
So, four stars for now, but with a recommendation that the vast majority of users avoid it.
An extremely useful addon. (I wish that such functionality were available for Chrome/Chromium).
The developer has let me know that version 2.1, corrected to account for the latest changes of adblock Plus, is available here: https://addons.mozilla.org/de/firefox/addon/4042/versions/?page=1#version-2.1This review is for a previous version of the add-on (2.0.1).
This add-on is a well-effected correction of a grossly misbegotten “feature”.This review is for a previous version of the add-on (1.3).
No, I wasn't "too stupid" to notice who was reviewing what. I was paying attention to reviews that claimed near perfection for very buggy versions. The fact that earlier versions were buggy didn't and doesn't somehow prove that later versions were not.
I got a great deal of use from the "undo closed tab" function when I was using Firefox 3.0.x. With 3.5.x, parts of this plugin became superfluous, but I'd like to get something with that undoing feature.
I'm really impressed with the commitment of telega's friends to pull the ratings of this plugin back up, but nothing else here is impressive. The plugin continues to be advertised as being compatible up to 3.6.1pre instead of admitting its issues in the long description. Many of the positive comments praise it as if it is perfect, when it works more like a beta release. Part of what should have been learned in the wake of the fiascos of versions 2.15 and 2.16 was the need for forthright communication.This review is for a previous version of the add-on (2.22b).
It doesn't mince words!
With version 2.15, telega betrayed the trust of his users. Users found their search fields hijacked, and their organization of the “dial” blithely discarded. The “support” site was simultaneously totally down.
Okay, well most or all of us screw-up terribly at some time or another. The question, then, is of what, if anything, we do about it.
Telega could have fixed the problems of the addon within *minutes*, if only by the simple device of issuing a version 2.16 that was basically just 2.11. With a little more time (at most hours) he could have issued a version that simply didn't have the hijacks.
If he couldn't get that quickly linked-up here, he could have told everyone in the “Long Description” how to uninstall 2.15 and reinstall 2.11.
Eventually, he did edit the “Long Description” to provide a URL to a less-screwy version, but first he wasted time trying to put the blame elsewhere.
(And now we have a bunch of SHILLS giving version 2.16 five stars, which it does *not* deserve — four would be believable, five is just a lie — trying to pump the score back up for this addon.)