May 3, 2009 at 17:18Noscript vs. Adblock plus
It turns out that recently became aware of the "war of extensions", which until then proceeded away from the user's eyes.
The conflicting developers of the fairly popular extensions Adblock Plus , designed to block unwanted ads on sites, and NoScript , aimed at increasing user safety by blocking scripts that run on pages.
After each update of the extension version, NoScript developers direct the user to their website (although they have written that such an action should be performed only in the case of a significant update *), where they also place ad units that Adblock Plus should, in theory, cut out. For a long time, a bug in the anti-advertising extension allowed NoScript developers to add their site to the Adblock exclusion list. When Vladimir Palant (Adblock Plus developer) corrected this error, NoScript developers took an unfair step and built code into the next version of their brainchild aimed at disrupting Adblock Plus.
After this became known, a complaint was filed in Mozilla and NoScript got a new version, already without malicious code. However, a little later, the extension was updated again and added a subscription * to Adblock Plus, in which NoScript sites were listed in the so-called “white list”, which again disrupts the operation of the anti-advertising extension.
Once again, a complaint was filed, and once again this functionality of NoScript was removed from dubious utility ... How long ...
For details, see the Adblock Plus developer’s blog
Mozilla reacted promptly by posting a number of changes to the AMO policy .
* I advise you to check the settings of your extensions, if you have never bothered yourself with this and turn off all these "usefulnesses" that are unnecessary for you
Updt. For those who do not understand what the fuss is: One extension intentionally interferes with the work of another extension, prevents it from functioning and is caused not by technical problems, but by the author’s desire to make more money.
Updt. Apologies by NoScript
The conflicting developers of the fairly popular extensions Adblock Plus , designed to block unwanted ads on sites, and NoScript , aimed at increasing user safety by blocking scripts that run on pages.
After each update of the extension version, NoScript developers direct the user to their website (although they have written that such an action should be performed only in the case of a significant update *), where they also place ad units that Adblock Plus should, in theory, cut out. For a long time, a bug in the anti-advertising extension allowed NoScript developers to add their site to the Adblock exclusion list. When Vladimir Palant (Adblock Plus developer) corrected this error, NoScript developers took an unfair step and built code into the next version of their brainchild aimed at disrupting Adblock Plus.
After this became known, a complaint was filed in Mozilla and NoScript got a new version, already without malicious code. However, a little later, the extension was updated again and added a subscription * to Adblock Plus, in which NoScript sites were listed in the so-called “white list”, which again disrupts the operation of the anti-advertising extension.
Once again, a complaint was filed, and once again this functionality of NoScript was removed from dubious utility ... How long ...
For details, see the Adblock Plus developer’s blog
Mozilla reacted promptly by posting a number of changes to the AMO policy .
* I advise you to check the settings of your extensions, if you have never bothered yourself with this and turn off all these "usefulnesses" that are unnecessary for you
Updt. For those who do not understand what the fuss is: One extension intentionally interferes with the work of another extension, prevents it from functioning and is caused not by technical problems, but by the author’s desire to make more money.
Updt. Apologies by NoScript