Perhaps the solution is some sort of code of conduct for advertisers. If ads are discreet and respectful of the viewer then I'd certainly be prepared to stop blocking them.
Perhaps the solution is some sort of code of conduct for advertisers. If ads are discreet and respectful of the viewer then I'd certainly be prepared to stop blocking them.
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.
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'm not curious enough to go and try it, though.
It turns out that only about 20 rules covered 99.5% of the _really_ annoying ads, whilst still leaving the OK ones. Adding those rules wasn't difficult, or annoying, or time consuming - just click and block when irritated.
The nuclear option (easy list) gets everything - even ad words - despite the fact that I don't mind them very much. The ABP developers really shouldn't make that the default, because I don't think people realize what they are signing up to. I don't object to them having the option, but it shouldn't be the default.
Witness Adsense, which started off with text only, but now has full flash capabilities.
What is the solution to the problem? I don't think there is one.
Perhaps the rise of the paid app will provide a way to reduce ads, just like cable tv has done, but this will only be a niche. (I'm speculating there.)
The way I see it, there is an implied contract between a website and a viewer. The website says, "well you get to look at my content for free and you will not have to pay for all the work I have done creating the content and serving it to you, but in exchange you should see and consider the various advertisements and deals we are offering."
Again you do not have to use the website, but if you do you should not block the ads.
Ad blocking means the market will never correct itself. You're cutting off the feedback loop.
If an ad annoys you, just don't visit that website again! Simple. It's not like there's a shortage of websites to visit.
edit: Yeah downmod me. It's a crazy idea! If you go into a shop, and the owner beats you with a bat, you'd resolve to wear full body armor when shopping from now on, and go right back there wouldn't you.
If there's an article on here from nytimes, I just don't bother with it any more. They have a paywall/subscription thingy and I just can't be bothered to google for login details.
But it's fairly simple to just block sites that annoy you - firewall/hosts/etc
If an ad annoys you, just don't visit that website again! Simple. It's not like there's a shortage of websites to visit."
Doesn't this depend on how ad blockers work?
If my browser fetches some HTML, and it includes an img ref to some ad site, my blocker might a) prevent the fetching of that resource, or b) allow it to be fetched, but block the rendering.
I'm pretty sure blockers use the first technique. So, visiting a site with an ad blocker ups a site's hit count, but adds nothing to the eyeball count for the ads. Fro the ad-tracking POV, it's as if you never visited.
It may very well be the sort of feedback that's needed.
If you really want to be more active about this you're better off writing to the site owner with your concerns than simply not visiting the place.
If my site gets no traffic, how will I know if it's because of the ads, or crappy content?
I do use flashblock/click to flash (which has the side effect of hiding the most offensive video ads). But any site that becomes unbearable with ads, I move on, and don't go there again. I would suggest it is time to avoid those sites.
Can you explain why not?
Unless there's some explicit prior agreement, I have no obligation to use my resources to render something in some specific manner, or at all.
Online ads fall into the same technological mismatch as online music. It's the application of solid-to-the-touch thinking to a fluid digital medium.
Web pages are not print. Don't base your business model on a different medium. (Ask the RIAA how well that works out.)
My browser requests some HTML; what it does with it on my end is up to me. If I don't want to waste time and resources making additional requests for other content, that's my business. If I don't want to render everything specified in the HTML, that's my choice. If I want to skip elements, apply custom CSS, block scripts, all are my choices.
And you better go tell Google their business model doesn't work before we're all left without a search engine!
Absolutely! It's my choice what I will render on my machine, and it's the server's choice what it will send me when I make a particular request. If they are capable of detecting when I've blocked ads and choose to deny my request for the content, that's well within their rights.
Then again, Ars is one of the few sites that will actively ban your account if you use ad blocking. But so far, I think they've only removed accounts for comments/forums, not the whole shebang.
Split test it first of course if you are reading this Ken!
OK, but the assertion was that it was unethical, not that it was unreasonable.
I agree that there's a downside and I may end up spiting myself, but it's not unethical for me to do so.
2) When an ad annoys you, enable your ad blocker for that site.
3) If you actually enjoy the content the site provides, you should let them know why you're blocking their ads so they can fix the problem. Otherwise, if everyone does what you do, the site will cease to exist.
3) You surely know that, that is a waste of time, 1. they already know, 2. they won't respond or do anything
"Right-click on a banner and choose “Adblock” from the context menu — the banner won’t be downloaded again. Maybe even replace parts of the banner address with star symbols to block similar banners as well."
The AdBlockPlus documentation explains how to limit specific rules to certain sites. (EDIT: http://adblockplus.org/en/filters#elemhide_domains) If you get filters from someone else, you're probably blocking ads that don't bother you on sites you enjoy, which sounds counterproductive to me.
(I'm actually surprised more sites haven't started responding by proxying ad content through their own servers to make it harder to block.)
The Ars thread touches on this, where Kurt mentions that Doubleclick's ad deployment isn't smart enough to detect flash-blockers and serve a static ad, and Ars isn't permitted to replace Doubleclick's deployment code.
Also your effectively blocking a particular ad supplier not a domain that has a poor ad policy.