News for hackers. Stuff that matters.

A comment on The Problem with AMP. Parent comment

Re:The Problem with AMP by paradite on Monday January 16, 2017 @11:23PM (#13415183)
Ah I didn't know this.

I run a WordPress blog. From the documentations of Google and WordPress AMP plugins, I have always thought that the user will be directed to "originalurl/amp" on my domain when they click on the Google link on their phone. Now that I see it's a Google domain, this is really weird.

[ Parent | on HN ]
Re:The Problem with AMP by jshen on Monday January 16, 2017 @11:25PM (#13415193)
It's not an AMP thing per se, it's how Google handles AMP in search results.
[ Parent | on HN ]
Re:The Problem with AMP by wheelerwj on Tuesday January 17, 2017 @05:56AM (#13416483)
No, its explicitly an AMP thing. Google serves the user a cached version of your page directly from its servers, hence the google.com/amp/ url
[ Parent | on HN ]
Re:The Problem with AMP by blntechie on Wednesday January 25, 2017 @04:17AM (#13479946)
No, it's not. See Nuzzel's implementation of AMP, it opens the AMP version on the host.
[ Parent | on HN ]
Re:The Problem with AMP by jshen on Tuesday January 17, 2017 @11:22AM (#13418762)
True, but you can serve the AMP page directly from the host.
[ Parent | on HN ]