GµårÐïåñ wrote:Am I missing something? This whole issue with ABP, how come I am not experiencing any issues when visiting noscript related sites?
Because you're up-to-date with latest development version, where the issue is fixed.
What is going on exactly with them escalating updates against noscript?
The new guy behind Easylist, Ares2, who took on Rick's duty when he regrettably passed away, has been running a crusade against all the InformAction web sites in the past two weeks, issuing more than 30 updates (the ones I counted, even 4-5 per day) specifically targeted to noscript.net, flashgot.net, informaction.com and hackademix.net.
Current Easylist lines affecting InformAction sites are the following:
Code: Select all
/flashgot.net/*$script,subdocument,xmlhttprequest
/hackademix.net/*$script
/noscript.net/*$script,subdocument,xmlhttprequest
/oss.informaction.com/*
informaction.com/*$script,subdocument,xmlhttprequest,domain=flashgot.net|noscript.net|software.informaction.com
flashgot.net#*(href*=informaction)(href*=com)(href*=%62)
flashgot.net#*(href*=informaction)(href*=com)(href*=flashgot)
flashgot.net#*(href*=oss)(href*=informaction)(href*=com)
flashgot.net#ul(class=tla)
noscript.net#*(href*=informaction)(href*=com)(href*=%62)
noscript.net#*(href*=informaction)(href*=com)(href*=noscript)
noscript.net#*(href*=oss)(href*=informaction)(href*=com)
As you can see, pretty much everything is disabled.
1.9.2, together with the long awaited bookmark-based syncrhonization feature, deployed a countermeasure meant to prevent automated subscriptions from affecting these sites, which NoScript and FlashGot development depends upon. Unfortunately this countermeasure proved to be overzealous, because it unwillingly disabled also blocked objects reporting
on these sites: therefore user was unable to block my ads even if he really wanted to (short of disabling active content using NoScript itself).
I promptly fixed this in subsequent development versions, which enable users to block ads on these sites as well
if they wish to.
However I decided to make this work-around simpler and more apparent to users, for transparence sake: so next stable releases will just add an explicit whitelist site filter, also providing instructions about disabling such a filter for those ABP users who don't know how to do it and are determined not to see any ad supporting NoScript and FlashGot development.
@
pirlouy:
there's no point in asking them why, it's "because ads are inherently bad and we don't care if we ban every web technology from your sites in order to block them".
And this is not an accident: as I said I've seen at least 30 different variants of the above piling up during the past two weeks. A lot of work, surely intentional.