Accelerated Mobile Pages

 Accelerated Mobile Pages  (AMP) is a Google-led project that (often) speeds up a subset of HTML through caching and dependencies on Google infrastructure.

IndieWeb Support
The pull request https://github.com/ampproject/amphtml/pull/499 by adds h-entry support to AMP example(s) and thus makes AMP more IndieWeb friendly by default

The PR was subsequently closed with the comment "We decided to remove metadata requirements from AMP." See: https://github.com/ampproject/amphtml/pull/593

Articles
W3C TAG finding (note, different meaning here of "distributed" (more like "content distribution") than what is usually mean by "distributed web")
 * : "Given the higher page RPMs and subscriber conversion rates of a non-AMP page, pulling the plug on AMP looks like an easy win for both programmatic and consumer revenue. And most importantly, we regain full control of the user experience. And that’s perhaps the biggest upside."
 * Tweet announcing the article: "The data is in. Just drop AMP. You'll be fine"
 * Copy of post on wordpress.com
 * Copy of post on wordpress.com
 * Copy of post on wordpress.com

XML like fragility
It appears that initial implementation(s) of AMP HTML consuming code treat it similarly to old XML consuming code, which is to fail in a fragile way, e.g. as noted in https://web.archive.org/web/20190405153959/https://twitter.com/bryanrieger/status/651782717676216320

 Screenshot of an Android device showing www.google.com trying to display an article from m.nydailynews.com with only a sad-mobile-device graphic and an error message: "Sorry, this page is not valid AMP HTML" followed by a footer link to continue to www.nydailynews.com.

Additional citations:
 * iOS screenshot of problem: https://twitter.com/shinypb/status/733302396995010561 "When developers turn their problems into users' problems: AMP, following in XHTML's proud footsteps." https://pbs.twimg.com/media/Ci02oS7UYAEsot-.jpg

Criticism

 * Hacker News discussion
 * via @jevdemon: "AMP is poisonous to the underlying concept of an open internet"
 * Hacker News discussion
 * WICG Content Performance Policy draft
 * Hacker News discussion
 * via @jevdemon: "AMP is poisonous to the underlying concept of an open internet"
 * Hacker News discussion
 * WICG Content Performance Policy draft
 * via @jevdemon: "AMP is poisonous to the underlying concept of an open internet"
 * Hacker News discussion
 * WICG Content Performance Policy draft
 * Hacker News discussion
 * WICG Content Performance Policy draft
 * Hacker News discussion
 * WICG Content Performance Policy draft
 * Hacker News discussion
 * WICG Content Performance Policy draft