Earlier quoted context omitted.
I think it will be a good change if publishers were forced to sell/deliver their own ads. The problem has always been third-party ad networks that track you across the web and sometimes delivers malware. Publishers have never had to take ownership for the ads they serve and the user experience has suffered. The way forward is native ads (no, native ads aren't advertorials) like podcast ads, radio ads, or sponsored po…
even big publishers like Yahoo can't do that because there's an average of 20 companies between then and the brands advertising. publisher would love to be alone in the field and pocket the .20 per click. but ad agencies go a long way to doubt the publisher reports etc and try to pay less. every month a new layer show up, with the sole promise of allowing the ad vendor to pay less for the publisher. the fad du jour i…
Introduction to WebKit Content Blockers
41–49 of 49 posts
Re: Introduction to WebKit Content Blockers
#42Earlier quoted context omitted.
I'd take you more seriously if you referred to them as "ad supported websites" rather than "free" websites.
I think "free" is the most accurate succinct terminology to be used here, when used with it's most common definition. An ad-supported site/service can still cost money to use (e.g. Hulu Plus), so just referring to a site as ad-supported to distinguish the business model is no clearer than calling it free. The way to resolve this is to be more explicit, such as saying it's "monetarily free". But we all knew what was m…
Some dudes here have autism. That or they like to be a pain in the ass...
Re: Introduction to WebKit Content Blockers
#43Apple: "We will allow ad blockers for Safari in iOS9. By the way, here's our new News app, which serves unblockable iAds"
Re: Introduction to WebKit Content Blockers
#44Firefox is also dabbling with built-in tracking protection ( https://news.ycombinator.com/item?id=9594158 ). I'll be curious to see how Google faces this trend with Chrome going forward. Apple may be able to get away with enabling users to block web ads while serving them native ads (in the guise of privacy), but if Google tried to do the same (i.e. with Google-served ads being somehow "blessed" by virtue of not shar…
They can do the same justification AdblockPlus does: Don't disable unintrusive ads, only intrusive ones, and thus allow google text ads. And yes, the adblock devs were given money by google shortly before making that choice.
(No offense, but you're an anonymous writer on the internet.) Do you know of a URL or something I can use to verify that statement?
Re: Introduction to WebKit Content Blockers
#45Earlier quoted context omitted.
They can do the same justification AdblockPlus does: Don't disable unintrusive ads, only intrusive ones, and thus allow google text ads. And yes, the adblock devs were given money by google shortly before making that choice.
>the adblock devs were given money by google shortly before making that choice. (No offense, but you're an anonymous writer on the internet.) Do you know of a URL or something I can use to verify that statement?
I was using Adblock Plus, but this made me think a lot about this. Now, I'm using Privoxy + NoScript with custom filters.
Re: Introduction to WebKit Content Blockers
#46Earlier quoted context omitted.
Are free websites going to last much longer if we keep attacking ads?
Ads aren't being attacked, they're being ignored. This is a reflection of that.
Re: Introduction to WebKit Content Blockers
#47Earlier quoted context omitted.
I think "free" is the most accurate succinct terminology to be used here, when used with it's most common definition. An ad-supported site/service can still cost money to use (e.g. Hulu Plus), so just referring to a site as ad-supported to distinguish the business model is no clearer than calling it free. The way to resolve this is to be more explicit, such as saying it's "monetarily free". But we all knew what was m…
> But we all knew what was meant, so why bother? Some dudes here have autism. That or they like to be a pain in the ass...
In the meantime, I'll just politely ask: Please stop doing that.
Re: Introduction to WebKit Content Blockers
#48Earlier quoted context omitted.
> But we all knew what was meant, so why bother? Some dudes here have autism. That or they like to be a pain in the ass...
I am desperate for the time when my karma is high enough to down vote people who use "autism" as a means to condescend or insult. In the meantime, I'll just politely ask: Please stop doing that.
Please don't post comments like this, though, which only dilute the thread further.
Re: Introduction to WebKit Content Blockers
#49Firefox is also dabbling with built-in tracking protection ( https://news.ycombinator.com/item?id=9594158 ). I'll be curious to see how Google faces this trend with Chrome going forward. Apple may be able to get away with enabling users to block web ads while serving them native ads (in the guise of privacy), but if Google tried to do the same (i.e. with Google-served ads being somehow "blessed" by virtue of not shar…
Is it a guise of privacy when iAds is actually more private? Google has already done this with blocking Flash ads which blocks their own ad network as well.