3 ms·

Why can't non-AMP pages be safely prerendered?

• lern_too_spel 6y ago
  Because doing so would communicate with the publisher's web server before the user has clicked on any results, deanonymizing the user to the publishers of all the results on the page. This is the entire point of AMP, yet 90% or more of the commenters on AMP articles don't understand it, which makes the comments completely useless.
  • jakelazaroff 6y ago
    Is there a source for this claim? I’ve never read anything about AMP that claims the intent is privacy. Furthermore, I don’t see why AMP specifically is needed for what you describe — it seems to me that Google could do the exact same thing with normal webpages.
    • lern_too_spel 6y ago
      > I’ve never read anything about AMP that claims the intent is privacy. Why else do you think it loads from Google's cache? > it seems to me that Google could do the exact same thing with normal webpages. Nope. The publisher needs to opt in to having their content served by Google; and the ad metrics, analytics, and login need to be delayed until the user clicks on the result. That can't happen without cooperation from the page. Hence AMP. I don't even do web development, and the design of AMP is mind-numbingly obvious even to me.