Re:Google Reverses Its Decision to Ban Ad Blocking Apps from...
by tomjen3 on Thursday February 11, 2016 @04:08PM
(#11083274)
Ads from third-parties are supposed to be placed in special amp-ad elements. Those would be trivial to block. Ads that are served as standard images would probably be limited to blogs that deal directly with advertisers (e.g what slatestarcodex does) which is about as inoffensive as it gets.
Re:Google Reverses Its Decision to Ban Ad Blocking Apps from...
by ocdtrekkie on Thursday February 11, 2016 @02:52PM
(#11082690)
Their text wrapping on that page is atrocious. o_o
Go
ogle
Ac
celerated
Re:Google Reverses Its Decision to Ban Ad Blocking Apps from...
by ocdtrekkie on Thursday February 11, 2016 @03:33PM
(#11082989)
Some testing: Apparently the text flows fine in Chrome. The AMP team would like you to believe their open standard that should be good for everyone everywhere has a website that only renders correctly in their own browser.
https://www.ampproject.org/docs/support/faqs.html#who-will-b...
https://www.ampproject.org/docs/support/faqs.html#how-do-acc... I imagine that means Google will be caching AMP pages in full, so if your search turns up an AMP page, it will be served from Google's CDN. Presumably, it will be more difficult to determine what is an ad if it's all cached, but maybe ads are an exception to cache -- you can't target a static ad very well.