Since there's no technical reason for it to stay, what Google decides to do here will be telling.

Are you suggesting they may be planning to leave the AMP bar at the top of the page? Even though they just went through a "multi-month long effort" with the explicit goal of removing that UI in favor of using the real URL bar?

Yes, I am. At a minimum, I suspect it stays for AMP content that's in the carousel area of search results. I wouldn't be surprised if it stayed on all AMP results.

I read the post top to bottom and it never mentions anything but changing the url. It doesn't say that top AMP banner thing is going away.

If they change the URL, doesn't the top banner _have_ to go away, since the content of the page is now fully controlled by the host displayed in the URL bar?

A CDN can inject content, it's often touted as a feature. I'm suspicious because they don't explicitly say the bar is going away.

The OP says they're planning to use the Web Packaging standard. That standard prevents third parties (like Google) from injecting content into the packages by requiring the page to be signed by the original site's private key.

That's how they're able to display the original page's URL in the browser without that practice being extremely misleading.

I expect that they'll be providing some tools for people to generate the packages - and that tool can inject the top bar if it wants. It remains to be seen whether Google will provide search-results priority to "AMP" webpackages not generated with Google's tools (I think we'd all hate it if they didn't, but there's no obvious reason that they have to).

In particular, one obvious way to implement this would be to have everyone sign a static webpackage that includes a JS loader that pulls resources from www.google.com/amp/ via XHR/CORS (using ServiceWorkers I guess?), which would only need to be signed once, and send that over to Google. Then the infrastructure continues to work the way AMP does today - you just upload actual AMP-compatible web pages to your actual website, and Google downloads and caches them. Probably this webpackage would just include a single script tag that pulls the loader itself from Google, so that Google can apply updates to the loader without having to bother you again.

The webpackages spec talks more directly about signing the actual data, which would be way better for the web, but it's not obviously better for Google and for publishers already invested in AMP, so we should be cautious that maybe Google does not mean this and means something that's easier for them and retains the lock-in.

Doesn't amp require including amp specific JavaScript? That would jump right past any need for it.

If the bar is going away Google can help themselves by saying that specifically. I'm not the only one that hates that thing.

There are other browsers...

sadly not used enough...

Even with these changes the top bar does serve one purpose, it tells the user that "something is different about this page". One thing I fear is visiting a web page, and having no hints that the content wasn't loaded directly from the target website.

Instinctively I agree with you, but I am having trouble convincing myself that this is fundamentally different from a CDN. In fact it seems better than a CDN - the relevant private key remains with the website authors, and is not held or controlled by the CDN. I don't get any warning in the browser that https://www.cnn.com is delivered by and signed by Fastly (unless I click to see the cert and see Fastly in the OU); what makes a webpackage of amp.cnn.com, signed by a key actually held by CNN's IT staff, worse?

(Also, if we think this is worth indicating, it should be done by the browser itself, not by the web page voluntarily including some CSS.)

Why though? With the changes announced in this post (e.g. using the web packaging standard), loading an AMP page from Google's servers will have pretty much all the same security guarantees that loading it from the origin's servers would have.

The web package definitely originates at the origin, but is it up-to-date? While I assume the web packages have expiry dates that the CDN servers would respect, this doesn't give the full control that Cache-Control headers do.

And in terms of functionality, does the AMP web version have all the functionality of the normal site? Often this is something I see missing on AMP sites. A top-bar gives you the ability to get back to the full site.

> The web package definitely originates at the origin, but is it up-to-date? While I assume the web packages have expiry dates that the CDN servers would respect, this doesn't give the full control that Cache-Control headers do.

I think it's the other way around - webpackages include Expires: headers for each resource that are signed by the origin, so the browser decides whether to trust it or not, or maybe to render it anyway but show a staleness indicator. But if you're using a CDN, the CDN implements caching on its own (hopefully following the origin server's instructions or the customer's instructions in a control panel, but no guarantee) and all headers are entirely controlled by the CDN.

> And in terms of functionality, does the AMP web version have all the functionality of the normal site?

On the technical side, this is now the origin's decision, not Google's - they can include whatever functionality they want or whatever links they want in the webpackage. It's not really different from having a mobile site that has a "View full site" link, or worse, doesn't have one and also misdetects your browser.

I think I agree that in practice it matters a lot what people choose to do, and whether Google adds restrictions for what sorts of webpackages count as "AMP" for the purpsoe of special treatment on the search results page.