Earlier quoted context omitted.
Honestly, aren't your comments as much an example of Apple bias as what you're commenting on, but with the sign reversed?
If you look at moves made by Apple in the iPhone era it becomes quite clear and does not require bias. - Ban flash. Biggest competition to native apps. - Cripple the iOS web browser just enough that web apps trying to have native style performance will struggle. - Release their own map to push Google out of their ecosystem. When that didn't work now they are trying this. Apple's business model is pretty simple. Aquir…
The adblocking revolution is months away
171–180 of 355 posts
Re: The adblocking revolution is months away
#172Earlier quoted context omitted.
How do you block them?
Hosts file, I assume
Apple denies the user reasonable control of the device they purchased. (Denying access to the HOSTS file is unreasonble in my opinion.)
But Apple does not (yet) exercise control over the network(s) that the user has joined.
As long as the user can still control at least some aspects of her own network (yes, she still can), then the user can block ads.
In my case, I use DNS to block ads. It is remarkably effective. But there are certainly other ways to do it.
Re: The adblocking revolution is months away
#173I completely understand why people use Adblock - it improves the user experience. Ironically hiding adverts is a just a side-effect; the improvement comes from speeding up page loads, and cutting down on cpu usage and bandwidth use. (I install Adblock for my mother to stop her seeing scams, but that's another thing entirely.) I've spent the past week optimising How a Car Works for speed (mobile is 55% of our traffic…
Thats one of the reasons I like uBlock origin- supposedly, it says the ad was displayed/clicked on a webpage, which means I don't deal with ads and websites don't deal with money loss.
[0] https://github.com/gorhill/uBlock/wiki/Does-uBlock-block-ads...
Re: The adblocking revolution is months away
#174Earlier quoted context omitted.
Honestly, aren't your comments as much an example of Apple bias as what you're commenting on, but with the sign reversed?
If you look at moves made by Apple in the iPhone era it becomes quite clear and does not require bias. - Ban flash. Biggest competition to native apps. - Cripple the iOS web browser just enough that web apps trying to have native style performance will struggle. - Release their own map to push Google out of their ecosystem. When that didn't work now they are trying this. Apple's business model is pretty simple. Aquir…
Google, Mozilla disable Flash over security concerns http://www.marketwatch.com/story/google-mozilla-disable-flas...
Even this Flash proponent admits, "Jobs was slightly ahead of his time" in You don't have to be a villain to say Flash must die* http://www.macworld.com/article/2948131/software-web/you-don...
-
Banning Flash has been a boon to HTML5 uptake.
YouTube Switches to the HTML5 Player in Chrome http://googlesystem.blogspot.com/2014/05/youtube-switches-to...
RIP Flash: Why HTML5 will finally take over video and the Web this year http://thenextweb.com/dd/2014/04/19/rip-flash-html5-will-tak...
How Adobe Is Moving on From Flash to Embrace HTML5 http://www.cio.com/article/2376661/internet/how-adobe-is-mov...
In other words Apple has helped HTML5. Intentionally crippling the iOS web browser? What usaphp said.
-
As to Maps, Google pushed themselves out: Apple ditched Google Maps over turn-by-turn navigation spat http://news.yahoo.com/apple-ditched-google-maps-over-turn-tu...
Re: The adblocking revolution is months away
#175I completely understand why people use Adblock - it improves the user experience. Ironically hiding adverts is a just a side-effect; the improvement comes from speeding up page loads, and cutting down on cpu usage and bandwidth use. (I install Adblock for my mother to stop her seeing scams, but that's another thing entirely.) I've spent the past week optimising How a Car Works for speed (mobile is 55% of our traffic…
Thats one of the reasons I like uBlock origin- supposedly, it says the ad was displayed/clicked on a webpage, which means I don't deal with ads and websites don't deal with money loss.
Where exactly does it say this?
Re: The adblocking revolution is months away
#176Re: The adblocking revolution is months away
#177Earlier quoted context omitted.
That's too simple. Apple (and others) have relentlessly tried to optimize power saving. People like phones with a good battery time, plus I assume that there can be significant cost saving if you can use smaller capacity batteries. They have probably come to a point where a significant amount of power use during mobile browsing is caused by ads (both rendering and the extra network use that it incurs). Blocking ads c…
I would venture to say that the relentless push to move as much as possible to the client has much more impact on battery life than the handful of ads we typically see.
Re: The adblocking revolution is months away
#178Re: The adblocking revolution is months away
#179Earlier quoted context omitted.
Theoretically, you could shift the responsibility of displaying ads and tracking users to the publishers, with requirements to publish back to the ad networks granular information about every impression. The ad networks could then check for cheating by randomly accessing the publishing website to make sure all the requests are reported back by the publishers.
Or shift the responsibility for displaying content onto the ad network! At least the page might load more quickly if Google are serving it.
Re: The adblocking revolution is months away
#180Earlier quoted context omitted.
That's too simple. Apple (and others) have relentlessly tried to optimize power saving. People like phones with a good battery time, plus I assume that there can be significant cost saving if you can use smaller capacity batteries. They have probably come to a point where a significant amount of power use during mobile browsing is caused by ads (both rendering and the extra network use that it incurs). Blocking ads c…
I would venture to say that the relentless push to move as much as possible to the client has much more impact on battery life than the handful of ads we typically see.
Every measurement (not many) I've seen suggest that screen (size/resolution) and network are the main culprits, outside of very intense CPU/GPU client (e.g. games). I don't think I've seen a really good analysis, though, so would be interested if you've got a reference.