[traek]

The original article is talking about traffic from Twitter to publisher sites, not traffic from Google to Twitter. Twitter never used AMP for pages on their own site.

In this case Twitter is the platform, not the publisher, and would absolutely have been able to not use the Google cache.

> Now, when using one of Twitter's mobile clients, users will be sent to the amphtml URL in their browser, instead of the link that was shared in the Tweet. Users will load this link directly, not via a page cache. [0]

[0] https://developer.twitter.com/en/docs/twitter-for-websites/a...