News for hackers. Stuff that matters.

A comment on Fight back against Google AMP (2018). Parent comment

Re:Fight back against Google AMP (2018) by lern_too_spel on Wednesday December 04, 2019 @12:22PM (#21704302)
The first part of your post is incorrect, AMP is instant because it is prerendered, which just using a CDN can't achieve.

The second part is correct. I hate Reddit AMP results, and I'm happy that Google is telling them to fix it. I'll be even happier when they and other search engines demote Reddit AMP pages that do not match the canonical pages.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by pkamb on Wednesday December 04, 2019 @12:41PM (#21704594)
> I hate Reddit AMP results, and I'm happy that Google is telling them to fix it.

Is there some kind of real news about Reddit AMP changing, specifically? I don't see that in the link.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by lern_too_spel on Wednesday December 04, 2019 @01:56PM (#21705634)
It says Google is validating that AMP pages match the content of the canonical pages and warning webmasters when they don't. I desuced that Reddit would get these emails because their AMP pages are the biggest offender that I regularly see.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by KirinDave on Wednesday December 04, 2019 @03:38PM (#21706643)
Can you talk more about the prerendering? I thought that was a thing Google does to many pages, not just AMP, when possible.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by lern_too_spel on Wednesday December 04, 2019 @06:06PM (#21708169)
It is unsafe to deanonymize a user to a website that the user did not even click on. That's why the page is served from the link aggregator's AMP cache.
[ Parent | on HN ]