Earlier quoted context omitted.
What part of sending a GET request to view a web page corresponds to ordering chocolate bar?
A GET request is not a request to view a web page, it is a request to receive the page. It is up the recipient to determine if and how the page should be rendered.
An update on Better Ads (Chrome native ad-blocking)
31–40 of 61 posts
Re: An update on Better Ads (Chrome native ad-blocking)
#32Edit: I guess another question, why aren't the answers to obvious questions like these readily available? Or am I just ignorant?
Re: An update on Better Ads (Chrome native ad-blocking)
#33So, basically all ad networks like zeropark, popads, popcash, propeller ads, will soon disappear?
Re: An update on Better Ads (Chrome native ad-blocking)
#34Earlier quoted context omitted.
Not a great analogy. We all know that HTML is an opt-in language, in that user-agents are designed to render the tags that they support and ignore the ones they don't. My user -agents do not support ads at all.
Your glasses (or AR goggles) when you walk into the store would correspond to the HTML renderer here.
That sounds great.
Re: An update on Better Ads (Chrome native ad-blocking)
#35An attempt by Google to take over the Adblocking market and thus maintain their own whitelist which will obviously not block Adsense ads. I have already moved over to firefox
> maintain their own whitelist which will obviously not block Adsense ads You make this sound like some kind of trick. The stated goal is to block especially obnoxious ads, of the kind adsense doesn't do. I can't say if it's going to be fair or not, but the way it treads adsense specifically isn't going to be the deciding factor.
That's your opinion, not everyone's. Luckily I'll easily be able to use what meets my definition of obnoxious with this feature (i.e. custom lists for this native blocker) instead of yours or this consortium's, right?
Re: An update on Better Ads (Chrome native ad-blocking)
#36I asked before, but never really got a good answer. Is this client side only? If not, how are they querying a server? And where can I download the full list of unacceptable ads/sites? And if I can't, why not? And finally, why does this have to be native instead of an extension? Edit: I guess another question, why aren't the answers to obvious questions like these readily available? Or am I just ignorant?
I think they need correlation of ads shown followed by an adblocker extension install so that they want to block such ads to prevent the growth in adblockers
Re: An update on Better Ads (Chrome native ad-blocking)
#37Re: An update on Better Ads (Chrome native ad-blocking)
#38There are no "better" ads. The only good ads are the ones I cannot see. My computer, my rules. Lately now blocking coin mining in addition to all ads, trackers, beacons, pixels, etc. I have the right to surf on my terms. Traffic to websites is a cost of doing business; don't try to recoup in ways that I never agreed to (mining), selling my data w/o my permissions, etc. You have to love the tripe in the article: "Bett…
>My computer, my rules.
This is really the only thing that matters. Ads are not a working model for monetization on the web for this reason, and this is non-negotiable. Ads are a non-starter. It's as simple as that. If anyone can't find a different way to support their content, then the web is better off without them. "Better ads" is putting lipstick on a pig - I'd sooner not invite the pig into my living room, thank you.
Re: An update on Better Ads (Chrome native ad-blocking)
#39I really hope a service will be created where I can pay for adfree content internetwide.
Re: An update on Better Ads (Chrome native ad-blocking)
#40If this effort by Google can somehow raise the quality of online ads from horrendous to just terrible, I'll reluctantly support it.