News for hackers. Stuff that matters.
Re:The Why and How of Google AMP at Condé Nast by niftich on Wednesday August 30, 2017 @07:51PM (#15137089)
Sure, they want their content to be read, to be "discoverable by the largest possible audience".

Meanwhile, "monetization benefits are less decisive and pending further analysis of our current implementation."

Publishers find a number of benefits to AMP -- revealed frankly in the article -- but the only reason they use it in the first place is because Google is where a lot of those eyeballs originate anyway. If Some Obscure Search Engine with ~1% marketshare reworked their mobile page to prioritize pages that adhere to some criteria of limitations, used an iframe to frame the content so that it loads inside their page, and threw in a free CDN to sweeten the deal, who'd retool their publishing infrastructure -- as excellently detailed in this post -- to publish in this format?

AMP enables an alliance of convenience between one of the top sources of traffic (Google), and the authors of long-form textual content reliant on advertising revenue. To the AMP team's credit, it does so by aligning closer than its competitors to how the web actually works, despite the Google-Search-on-Mobile page then acting as a captive newsreader.

Most user criticism of AMP is focused on Google-Search-on-Mobile stealth-morphing into a captive newsreader, while most publisher criticism of AMP is from sites outside of its target market trying out the tech and alarmed at the lack of traffic reaching their server, forgetting that offloading traffic at high volumes is a good thing. AMP isn't for people who are upset that Google is stealing your content; it's for publishers who want Google to expose their content to wide audience and hope to generate revenue through means that correlate to that reach.

Re:The Why and How of Google AMP at Condé Nast by RestlessMind on Wednesday August 30, 2017 @08:29PM (#15137237)
Just one nit:

> AMP enables an alliance of convenience between ... Google ... and the authors ...

The third party in that alliance is the end user who was a decent mobile browsing experience. As one, I absolutely love AMP. It guarantees that the page I am about to click on is not going to be horrible. So much so that these days, I actively seek out pages with AMP icon in my search results.

Re:The Why and How of Google AMP at Condé Nast by damnfine on Thursday August 31, 2017 @09:02AM (#15139944)
And I actively avoid them due to useability issues. To each their own.
Re:The Why and How of Google AMP at Condé Nast by s17n on Wednesday August 30, 2017 @08:24PM (#15137226)
I think most of the criticism of AMP is the URLs being messed up, which is something that will soon be fixed.
Re:The Why and How of Google AMP at Condé Nast by tyingq on Wednesday August 30, 2017 @08:35PM (#15137264)
I don't imagine most publishers would normally place a banner at the top of the page that someone else controls. With an [x] button that closes your page and goes back to that "someone else".
Re:The Why and How of Google AMP at Condé Nast by donohoe on Wednesday August 30, 2017 @08:57PM (#15137346)
No. This will not be fixed.

As long as they insist on using their CDN then this cannot be avoided.

Re:The Why and How of Google AMP at Condé Nast by s17n on Wednesday August 30, 2017 @10:13PM (#15137666)
It will be fixed client side - Safari is rolling this out in ios 11
Re:The Why and How of Google AMP at Condé Nast by hdhzy on Thursday August 31, 2017 @02:25AM (#15138514)
Do you mean the URL shared or displayed in address bar?
Re:The Why and How of Google AMP at Condé Nast by donohoe on Wednesday August 30, 2017 @10:24PM (#15137720)
Ah I get what you mean now. Am excited for that too.