- Joined
- 8 Apr 2003
- Messages
- 6,376
It seems as if the two script authors have had a little bother with each other lately and harsh words have been said by either side. Here is a little from the adblock site
And here is NoScripts response
So i dont know about you but i havent used NoScript in a while, and after this maybe with good reason, It appears the damage maybe already done for NoScript as there are a lot of one star reviews of the addon on the mozilla addon site - https://addons.mozilla.org/en-US/firefox/reviews/display/722
Recently I wrote about how not giving extension developers a good way to earn money might lead to very undesirable effects. The recent events give an impression of the kind of effects we should expect here. This is going to be about the popular NoScript extension which happens to make its money from ads. And to make sure that somebody sees these ads it goes pretty far. For example, it opens the changelog webpage (full of ads of course) on every single update of the extension, even though the NoScript FAQ claim that it happens only on major updates (yes, if you dig into it you will find the preference to disable this behavior – but how many people do that?). And updates coming roughly each week ensure that this page is opened fairly often. A problem is of course that NoScript will usually disable scripting and consequently also most advertising. That problem is being worked around by putting NoScript’s domains, Google AdSense and a few others on NoScript’s default whitelist (again, the overwhelming majority of users won’t go hunting for bogus entries in their whitelist). Given that NoScript proudly calls itself a security extension this means putting users at risk — for example, a while ago I demonstrated how an XSS vulnerability on a NoScript domain can be used to run JavaScript from any website, despite NoScript. This was countered by implementing anti-XSS measures rather than removing anything unnecessary from the whitelist.
And here is NoScripts response
IMPORTANT UPDATE FOR ADBLOCK PLUS USERS: NoScript 1.9.2.6 automatically and permanently removes the controversial "NoScript Development Support Filterset", with no questions asked.
I sincerely apologize with those ABP users who missed the information about it given on the AMO install page, on this site's install page, on the release note landing page (shown on updates) and in the FAQ http://noscript.net/faq#qa3_21
Not including a prompt asking for permission beforehand from the start has been a very wrong thing to do, and I want all the ABP users who felt betrayed to know how much I'm sorry for that. As a sign of good will, current NoScript 1.9.2.6 completely removes the filterset itself, if found there, on startup with no questions asked. Thanks for your patience.
-- Giorgio
So i dont know about you but i havent used NoScript in a while, and after this maybe with good reason, It appears the damage maybe already done for NoScript as there are a lot of one star reviews of the addon on the mozilla addon site - https://addons.mozilla.org/en-US/firefox/reviews/display/722