Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As a longtime iOS user browsing the web keeps getting worse.

These are getting bigger, they're more resource intensive thanks to 'waterfall' design. They push up my data usage.

They spam open the App Store, and are all around broken. Recently I can't watch videos on some sites because ads elsewhere on the page grab the click and pop a new tab open.

They take longer to load than the real content. Then they MOVE the real content AFTER I STARTED READING because it took them that long to load.

I've used a Flash blocked on my laptop for years, but I didn't used to care about blocking on iOS because it wasn't a problem.

That has ABSOLUTELY changed in the last year or two. Reader mode used to fix sites but as they do more stupid JS trickery that often doesn't work.

I keep running across articles I literally CAN NOT read on my phone due to these kinds of issues.

Ignore iAds and Goigle and privacy (all good points). This is starting to seriously degrade my iOS experience and I'm not surprised Apple was moved to do it.



You can block ads on iOS right now (but it's not easy): install 'privoxy' on a home computer and set up your iPad to use it as a proxy server.


Use Atomic Web or Mercury as your browser. Both will block ads. I've used AW for about 3 years on both my iPhone and iPads. I couldn't live without it.


[deleted]


Safari supports SPDY, I don't see why they wouldn't support HTTP2 at some point.

But that's a total red herring. HTTP2 won't help my phone load large image ads from ad networks faster. The connection overhead savings on the real site don't outweigh the giant image downloads either.

It doesn't matter what implementation you use, booting me away from content after the page already loaded is a HORRENDOUS usability mistake. Popover ads are terrible in the first place but waiting until I've read three paragraphs because the cell network is slow is moronic.

And it has nothing to do with Nitro. Safari is the base OS experience. Faster JS for 3rd party browsers wouldn't effect this as it's not an issue of JS speed. And you can't tell your customers "well if you want your experience to not suck download someone else's browser."

There is no neglect here causing this issue.


iOS 9 supports HTTP2




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: