Very revealing. I stopped using NoScript a while ago since it would not properly whitelist some sites. At the time I was wondering why the plugin was updated so frequently with very similar change logs each time. This post explains why. Interfering with other extensions' internal state is simply unacceptable. Firefox should consider sandboxing the browser extensions. Maybe they'll get to that after they implement Chr…
The plugin is updated frequently also because doing so lands itself in the Most Popular Add-ons chart. Giorgio has a history of pushing the limit to see what he can get away before backtracking when someone calls him out on it.
Attention NoScript users
41–42 of 42 posts
Re: Attention NoScript users
#42Adblock also blocks the behaviour of no-script... by blocking the ads. Both are doing wrong in a way... but not in others. It's a contradiction, but neither can claim to be the white knights... both are at best grey.
NoScript's behavior isn't the display of ads though, so AdBlock is _not_ directly messing with NoScript. It could be that the users installed AdBlock to block the NoScript ads. In this case, NoScript is giving the finger to the users opinion. At some point when the default behavior of two programs with similar feature-sets overlaps you just have to leave resolving them as an exercise for the user. But targeting the o…
That's what it does - it displays ads as part of its website on the extension update page. So those ads are part of the extensions behavior.
Obviously some users supported the NoScript author through the ads or donations. So by blocking those - and blocking the update alltogether - AdBlock was disrespecting what some of the NoScript users wanted.
My point still holds that both were not doing the best in the interest of their users, mozilla, or even themselves.
It was destructive all round.