News for hackers. Stuff that matters.

A comment on Google AMP – A 70% drop in our conversion rate. Parent comment

Re:Google AMP – A 70% drop in our conversion rate by realusername on Wednesday August 08, 2018 @09:47PM (#17721135)
Except there's NOTHING technically requiring google to serve AMP from their own domain. None of the speed benefits can justify that. AMP could just be another standard where the basic lib is preloaded on the browser.
[ Parent | on HN ]
Re:Google AMP – A 70% drop in our conversion rate by johncolanduoni on Wednesday August 08, 2018 @11:28PM (#17721469)
If you want to pre-load the page in the background in search results without allowing the site operator to track the user, they do need to serve it from somewhere they control.
[ Parent | on HN ]
Re:Google AMP – A 70% drop in our conversion rate by realusername on Thursday August 09, 2018 @12:06AM (#17721579)
You could just have an AMP doctype supported natively by Chrome (and whoever wants it) which does the same. Google just did not went that route.
[ Parent | on HN ]
Re:Google AMP – A 70% drop in our conversion rate by Vinnl on Thursday August 09, 2018 @03:43AM (#17722301)
They did announce that they still want to go that route, somewhat: https://amphtml.wordpress.com/2018/03/08/standardizing-lesso...
[ Parent | on HN ]
Re:Google AMP – A 70% drop in our conversion rate by johncolanduoni on Thursday August 09, 2018 @03:45AM (#17722309)
The destination server would still get a request on preload if there is no proxy operated by Google, no matter how you enforced the standard.
[ Parent | on HN ]
Re:Google AMP – A 70% drop in our conversion rate by realusername on Thursday August 09, 2018 @04:16AM (#17722446)
Yes, that's fine by me.
[ Parent | on HN ]