Adobe has abused our trust with a third party cookie blocking mechanism that just doesn't protect us without essentially making Flash worthless on many sites where we do want to use it. One of the few ways around it is to use NoScript to block JavaScript driving Flash by default, and then allow the ones we want to allow one by one. But why would I allow an ad network to track me across web sites just because I like Ars Technica?
So asking us to unblock Flash? Wow, I love arstechnica, but they know better than asking us to do that.
We are being asked to accept a particular type of ad technology that is fraught with problems, it's not ads we're blocking, it's widely abused technology that we're blocking. It's not for the pretty animations that Flash is used in many ads, it's for the third party cookies that track across sites.
Most people don't even realize how those Flash third party cookies track their movements across the net. But Ars Technica realizes, and so do I. Hell no!
Unfortunately, the advertiser then has to trust the publisher on how many users visited the site (or come up with something less intrusive that counts views).
Amazingly this trust has worked well enough for television and radio (and its advertisers) for decades.
On the web though, it's ridiculously easy to verify each request that there is no need for the trusted third party.
I can only speak for myself but a solution does not seem that far off (at least not to get me to see your ads). While I agree that some sort of code of conduct may be a good idea, I don't really see it working out in the long run what with everyone always being willing to sacrifice good will for a quick buck.
That said, I use NoScript in Firefox and I run it for other reasons than blocking advertisements and I don't have an ad-blocker installed. If I white list a website it means I made a deliberate choice to trust whatever it is going to throw at me. The most important thing here is that I did not allow any third party to serve me some random code (plain markup is fine). I have no way of telling whether the site I just white listed in fact knows what their external advertisers actually serve. And this is proven again and again by how site owners expect visitors to contact the site when they see an ad that is intrusive so that they can "nuke it". This to me makes it a no deal.
To kill two birds with one stone: Serve your advertisements from your own servers and if I want to read your content I have to make a choice whether to trust you and your webserver(s). If you violate my trust then I will go elsewhere and I am no longer a waste of your resources and you are not a waste of mine.
If I have for some reason decided to not let you run dynamic content on whatever device I am currently on you simply have to respect that or I leave. You still have the opportunity to serve me static ads, surely that's got to be worth something. You don't know my reasons for not white listing you (as this article states as well). What surprised me about this link was that I did not see a single advertisement on the page. This means they are all using JavaScript or Flash. Sorry, your loss. And eventually my loss as well since the website might not live to see another day due to lack of income.
Incidentally, easy white listing [of script execution] for sites is also the only thing stopping me from switching to Chrome today.