arstechnica.com — The NoScript Firefox extension faced a major backlash last week when users discovered that it was surreptitiously disrupting the operation of AdBlock Plus. The developers behind the two extensions turned the browser into a battleground as their conflict escalated. Mozilla has responded by proposing a new policy that sets boundaries for appropriate
May 4, 2009 View in Crawl 4
erickstevensonMay 5, 2009
Good thing I removed NoScript way before this event occured. I have been using AdBlock Plus since I installed firefox though. Anyway it was great that this was exposed and a new policy in firefox will hopefully stop this from happening again, I hate malwares.
yuttMay 5, 2009
To make paranoid people feel superior to others, while inconveniencing themselves and interacting with websites as if it was 1990. All while they mindlessly whitelist scripts on any site they use, without any indication of how safe it is, and thus make themselves as at risk as someone who doesn't use the addon at all.
dralezeroMay 5, 2009
What kind of sites do you visit so dangerously? Japanese animal pron?
uberdugerMay 5, 2009
@magamiako:I think I love you.
lanjackalMay 5, 2009
All I have to say is that I always use AdBlock Plus and have NEVER used NoScript.
buckrogers1965May 5, 2009
I like using both noscript and adblock plus. I think that both these plugins are great and work great together. I am going to keep using both of them.I love the default block all scripts on every site unless I allow them mentality. I don't want some random site being able to run scripts on my computer without my specific permission. From a security standpoint, denying every action and then only allowing specific actions is the most secure model. Yes, it can be more difficult, but it is worth it. Web developers need to make their sites degrade gracefully. There is no need to have submit buttons depend on scripting, for instance. There is no need to have a site depend on flash to see or navigate the site.
diggimatorMay 7, 2009
Or just uninstall NoScript? I live without it fine. I remember a user complaining about a digg JavaScript update last year because it didn't play well with NoScript. A solution that creates more problems than it solves is not for me.