News for hackers. Stuff that matters.

A comment on Kill Google AMP before it kills the web. Parent comment

Re:Kill Google AMP before it kills the web by discordance on Saturday May 20, 2017 @10:21PM (#14385387)
It feels like the principles (minus the tracking) of AMP should become a W3C spec. Surprised Microsoft and others haven't pushed for this.
[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by bsimpson on Sunday May 21, 2017 @04:25AM (#14386318)
What tracking?

I'm not aware of anything AMP does differently than non-AMP with regard to tracking, except that it's declared in a way that allows it to be cached+preloaded without falsely triggering analytics.

[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by discordance on Tuesday May 23, 2017 @04:55AM (#14399847)
When a user searches for an article on Google and clicks on an AMP link it never leaves google.com, even if the AMP link is an external entity.

Repro: 1. Search for some BBC news on google.com, click on an AMP link and load a BBC page 2. Notice that you're still on google.com and not on bbc.com

[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by deno on Sunday May 21, 2017 @05:25AM (#14386449)
Actually we could do even better and let the browser do the tracking and anonymize the data.
[ Parent | on HN ]