Google wants websites to adopt AMP as the default for building webpages
Google is also trying to get rid of URLs in Chrome, which dovetails with AMP certificate-signed content, <a href="https:&#x2F;&#x2F;www.engadget.com&#x2F;2018&#x2F;09&#x2F;05&#x2F;google-change-interact-urls-website-security&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.engadget.com&#x2F;2018&#x2F;09&#x2F;05&#x2F;google-change-interact-u...</a><p><i>&gt; So we want to move toward a place where web identity is understandable by everyone—they know who they&#x27;re talking to when they&#x27;re using a website and they can reason about whether they can trust them. But this will mean big changes in how and when Chrome displays URLs.</i><p>There&#x27;s an IETF proposal for certificate-signed web content (Web Packages) which can be rendered offline. The browser address bar will no longer show the URL of the web server (e.g. Google AMP), it will show the authenticated origin of the Web Package.<p>2017 IETF proposal by Google: 
<a href="https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-yasskin-webpackage-use-cases-00" rel="nofollow">https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-yasskin-webpackage-use-cas...</a><p>Video of a Chrome demo at 2018 AMP event, which looks like the latest Chrome proposal for hiding URLs in favor of “web identity”: <a href="https:&#x2F;&#x2F;youtube.com&#x2F;watch?&amp;t=9m03s&amp;v=pr5cIRruBsc" rel="nofollow">https:&#x2F;&#x2F;youtube.com&#x2F;watch?&amp;t=9m03s&amp;v=pr5cIRruBsc</a><p>There may be overlap in goals with W3C Web Publications, which is working to converge EPUB and Web: <a href="https:&#x2F;&#x2F;w3c.github.io&#x2F;wpub&#x2F;" rel="nofollow">https:&#x2F;&#x2F;w3c.github.io&#x2F;wpub&#x2F;</a><p>What happens if your “web identity” certificate expires or is revoked&#x2F;blacklisted?  Does your web identity certificate require a separate yearly fee from the domain name?<p>Edit: Comments from Chrome dev team manager,  <a href="https:&#x2F;&#x2F;twitter.com&#x2F;__apf__&#x2F;status&#x2F;1037057121961967616" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;__apf__&#x2F;status&#x2F;1037057121961967616</a> &amp; <a href="https:&#x2F;&#x2F;twitter.com&#x2F;__apf__&#x2F;status&#x2F;1037181065423515648" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;__apf__&#x2F;status&#x2F;1037181065423515648</a><p><i>&gt; URLs aren&#x27;t usable, but people are forced to rely on them for so much -- browsing, security, sharing. Expect to see changes to how Chrome displays identity in the coming year.</i>