11–20 of 74 posts
Why it's almost like the only way to deal with Apple users is to sell to them through Apple, and therefore give up at least 30%.
9 seconds of page load for ads is unacceptable. Mobile browsing has become a pita because of all those poor ads network, and i think once again (after the flash controversy) apple is going to save the web by making radical decisions like this one. It may very well be that mobile web content browsing becomes even more pleasant than using native apps thanks to that, since they too seem to fall for the trend of putting…
Apple isn't doing this to save the web, they are doing this so developers will be forced to create a native app to show ads and make some money. Easiest way to show ads in a native app on iOS... oh wouldn't that be iAd service in which Apple gets a cut of the profit?
What i think is that by making it harder to put ads in mobile web content, they'll make it more expensive as well, and thus push toward higher quality ad networks ( better targeting, better speed, better content).
Just like the end of flash saw an increase of quality SPA HTML5 frameworks.
The way it works is simple. You install an ad blocker, let's call it QBlock.
Then, QBlock goes to the websites and the ad networks to negotiate. If you want to reach our 1M users with your ads, you have to play ball with us. e.g.
* Keep ads to 15% of screen space
* Don't autoplay audio
* Don't exceed 15% of network traffic
* etc.
If you comply with our guidelines, we'll let your ads through. If you don't, tough.
Of course this assumes there are users who would prefer an ad blocker that lets responsible advertisers through as opposed to one that doesn't, but I believe that enough people do that it could work.
Earlier quoted context omitted.
yes, but if you read the article, the author states that was not blocked by the content blocker, he was just unable to get it to reappear.
If you look at his script the blocking system lets you hide html elements with css, too hide the app store banner all you have to do is inspect element in chrome, find the element id/class and set it to display none.
I really think a kind of lightweight collective bargaining is the answer here. The way it works is simple. You install an ad blocker, let's call it QBlock. Then, QBlock goes to the websites and the ad networks to negotiate. If you want to reach our 1M users with your ads, you have to play ball with us. e.g. * Keep ads to 15% of screen space * Don't autoplay audio * Don't exceed 15% of network traffic * etc. If you co…
This policy, for good or ill, annoyed many of the users: https://adblockplus.org/acceptable-ads
Ultimately, it lead to the popular fork:
https://addons.mozilla.org/en-us/firefox/addon/adblock-edge/
Earlier quoted context omitted.
yes, but if you read the article, the author states that was not blocked by the content blocker, he was just unable to get it to reappear.
If you look at his script the blocking system lets you hide html elements with css, too hide the app store banner all you have to do is inspect element in chrome, find the element id/class and set it to display none.
I really think a kind of lightweight collective bargaining is the answer here. The way it works is simple. You install an ad blocker, let's call it QBlock. Then, QBlock goes to the websites and the ad networks to negotiate. If you want to reach our 1M users with your ads, you have to play ball with us. e.g. * Keep ads to 15% of screen space * Don't autoplay audio * Don't exceed 15% of network traffic * etc. If you co…
That is very similar to what Adblock plus did. Many of the users were very unhappy, leading to forks of the project. This policy, for good or ill, annoyed many of the users: https://adblockplus.org/acceptable-ads Ultimately, it lead to the popular fork: https://addons.mozilla.org/en-us/firefox/addon/adblock-edge/
Earlier quoted context omitted.
If Apple wanted to, they could let the content blockers work for native apps as well. All in-app ads that I have seen are loaded over the same HTTP mechanisms. I guess they have chosen not to do so.
I'd be amazed if the SDK's UIWebView (whatever it's called these days) didn't have access to this in some future release. I doubt they'd apply it to generic HTTP calls on apps though - it would ruin the ad-supported app ecosystem and Apple aren't that daft.
Aww. I was hoping he also took care of the App Store banner using the content blocker. Would be great if those banners could be turned off.
I really think a kind of lightweight collective bargaining is the answer here. The way it works is simple. You install an ad blocker, let's call it QBlock. Then, QBlock goes to the websites and the ad networks to negotiate. If you want to reach our 1M users with your ads, you have to play ball with us. e.g. * Keep ads to 15% of screen space * Don't autoplay audio * Don't exceed 15% of network traffic * etc. If you co…