AMP Project Blog
amphtml.wordpress.com · Company blog · on HN since 2015
Official blog of the AMP Project, a Google-backed framework for fast-loading web pages, covering governance, URLs, caches and WorkerDOM.
What HN saysHN links it as the primary source for AMP announcements, including governance, Web Packaging for better URLs, and WorkerDOM.
31HN people shared it
15linked it in comments
17stories submitted
313story points
6 years agolast shared
2015people per year2026
Most-shared posts
- 1Improving URLs for AMP Pages7 people · 96 points · first shared 2018 · 108 comments on HN
- 2Standardizing lessons learned from AMP5 people · 92 points · first shared 2018 · 88 comments on HN
- 3An open governance model for the AMP Project3 people · 80 points · first shared 2018 · 113 comments on HN
- 4Bringing you up to Speed on AMP2 people · 14 points · first shared 2015 · 5 comments on HN
- 5Improving URLs for AMP pages2 people · 13 points · first shared 2018 · 2 comments on HN
- 6AMP: A year in review2 people · 3 points · first shared 2016 · discussion on HN
- 7WorkerDOM: Concurrency for JavaScript Programming with the DOM2 people · 2 points · first shared 2018 · discussion on HN
- 8Why amp caches exist2 people · first shared 2017
- 9AMP grows its footprint1 people · 3 points · first shared 2017 · discussion on HN
- 10AMP Is Two Years Old1 people · 2 points · first shared 2017 · discussion on HN
- 11Introducing Amp Ads1 people · 2 points · first shared 2016 · discussion on HN
- 12AMP Cache Updates1 people · 2 points · first shared 2016 · discussion on HN
- 13Live-updating AMPs1 people · 2 points · first shared 2016 · discussion on HN
- 14The Very Large Mobile Page Accelerator1 people · 1 points · first shared 2016 · discussion on HN
- 15Behind the Scenes at AMP’s New Very Large Mobile Page Accelerator1 people · 1 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
Ajedi32 · 2020-11-19
FWIW they announced their intention to do this over two years ago now, in March 2018:
> Based on what we learned from AMP, we now feel ready to take the next step and work to support more instant-loading content not based on AMP technology in areas of Google Search designed for this, like the Top Stories carousel. This content will need to follow a set of future web standards and meet a set of objective performance and user experience criteria to be eligible.
Source: https://amphtml.wordpress.com/2018/03/08/standardizing-lessons-learned…
jeffjose · 2019-01-30
The AMP team is working on the exact opposite, which is adopting Web Packaging [1] that fixes the URL issue you are describing.
https://amphtml.wordpress.com/2018/11/13/developer-preview-of-better-a…
[1] - https://github.com/WICG/webpackage
fulafel · 2018-10-02
Link to blog post: https://amphtml.wordpress.com/2018/08/21/workerdom/
tldr; aim is to bring scripting to AMP pages
nailer · 2018-09-18
Blogspam (and also from Vox media, who you may not wish to give advertising dollars to).
Original source:
https://amphtml.wordpress.com/2018/09/18/governance/
HN discussion:
https://news.ycombinator.com/item?id=18017224
wmf · 2018-09-18
A strict subset of HTML+CSS doesn't give 100% of the benefits of AMP and apparently at Google the perfect is the enemy of the good so they're going all or nothing on performance. Standardization of AMP is underway in the form of Feature Policy, Web Packaging, iframe promotion, Performance Timeline, and Paint Timing but it's going to take years. https://amphtml.wordpress.com/2018/03/08/standardizing-lessons-learned…
Vinnl · 2018-08-09
They did announce that they still want to go that route, somewhat: https://amphtml.wordpress.com/2018/03/08/standardizing-lessons-learned…
dmitriid · 2018-04-02
AMP tech leads especially. For a quick glimpse you can read this: https://amphtml.wordpress.com/2018/03/08/standardizing-lessons-learned…
ocdtrekkie · 2018-02-24
The same way they're trying to fix this problem with AMP: https://github.com/WICG/webpackage (see also: https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/…
Even if you can't package up and ship all of your traditional site to Google's CDN, you could do most of the burdensome/heavy bits. But then Google doesn't get to control your website and define the way it's allowed to look, which is what AMP is really for.
dontnotice · 2018-01-09
It's funny how no one was up in arms when facebook (the leading source of publisher traffic) did their version of accelerated pages.
AMP serves a purpose for the end user and it does so well, it loads instantly and doesn't consume much data in the process.
As for their "demands":
1. Google already states that AMP pages are ranked higher because they're faster to load.
2. I'm not sure if it's related but they they addressed that only yesterday: https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/
bryanlarsen · 2018-01-09
Doesn't https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/ address one of their two demands?
jopsen · 2018-01-09
then you didn't read yesterdays announcement:
https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/
Look at the underlying specs... They are talking about bundling web packages and signing them with TLS certificates, so that anyone can distribute them... and the browser can still verify the origin.
ninkendo · 2018-01-09
downvoters: this is 100% true. AMP has some nice standards on how to make a fast page but at the end of the day, google's re-hosting your page in a place where it can fetch in advance while obeying the same-origin policy, and clicking a result is the moral equivalent of unsetting a "display: hidden" attribute on the page.
AMP only works today because it's re-hosted inside the origin (google.com), so much that in order to fix this in the future, they'll have to rush out a new web standard and implement it in chrome (and hope other browsers do the same:) https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/
pgeorgi · 2017-06-09
It really depends on what you want to do: disseminate information (with a canonical URL that you control) or shovel users to your server?
In the former case, AMP caches are a reasonable compromise since it's really just a free CDN.
In the latter case, that cache is annoying because of how it needs to fit in the design of the contemporary web. See the last paragraph of https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exist/ for some ideas on how to improve the platform so the caches wouldn't be necessary for much of AMP.
matchu · 2017-01-23
Be sure to read Paul Bakaus's response, "Why AMP caches exist", to hear both sides of the issue. https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exist/amp/
(Though, actually, it's only a response in spirit; Bakaus's article was posted about a week earlier than Miessler's.)
I think the problem with the AMP cache model is that, because you need to link directly to the cached URL, you commit to exactly one cache provider. If Bing were to also implement their own validated AMP cache for Bing search results, you can't have one link point to both; you're either AMPed in Google results or in Bing results, and, by being marginally bigger, Google wins all of the pie. That's no good.
How might we change the AMP standard, or the trust model around AMP caches, to get the same performance wins while still enabling competition?
Zikes · 2017-01-23
AMP specifications allow for other cache servers, of which CloudFlare[0] has recently implemented one. You could implement your own if you like.
AMP also specifies that the canonical page URL should be used when sharing, though the cached URL is currently what's shown in the browser. Their last developer update[1] said they're working to address this, however for all relevant purposes Google's own systems already currently consider AMP traffic and results to be attributed to the original source.
[0] http://www.businessinsider.com/cloudflare-adopts-google-amp-2017-1
[1] https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exist/
> Google amends its cached AMP search results with Schema.org and OpenGraph metadata, so posting the link to any platform that honors these should result in the canonical URL being shared.