Suggestion: add reasons for blocking

[ironchefpython]

This is just a strawman, I haven't really thought through the implications.

What if, instead of a simple "curtains" link, there were a link that said, "already have", "use alternative", "not target audience". And instead of simply not loading the ad url, you sent an HTTP head request for the ad with a header set containing the reason you don't want to see the ad.

While I don't want to block ads that pay for the sites I enjoy for free, I am SO sick of seeing ads for Netflix all the time, when I'm already a subscriber. I don't want to see ads for Ford pickup trucks when I live in NYC. If you really want to "compromise" with Google, give them the information they crave in exchange for not showing their ad.

[n8]

Thanks for the suggestion @ironchefpython. That's an interesting idea about the multiple commands. I'll ponder that a bit.

As for the request back to a server recording the unwanted ads, I was definitely thinking along those lines too. Just hadn't had time to build that piece. Even in the current form I'd think it would be real helpful for ad networks and advertisers to get data on how often people are clicking "curtains" on their ad. So I might at the very minimum add a backend service people can opt-in/opt-out from which just records the curtains clicks and can dish that info to interested parties.

[ironchefpython]

So I might at the very minimum add a backend service people can opt-in/opt-out from which just records the curtains clicks and can dish that info to interested parties.

I would not be interested in this. Regardless of your intent, this backend service would seem too much like you're aggregating user behavior for resale.

This is why I suggested sending an HTTP HEAD request with a header explaining why you don't want to see that ad. The ad provider gets both an immediate notification the ad was rejected, and a reason. And there's no third party involved.