4 ms·
I don't understand. So now the URL bar won't always show where the page was actually loaded from? It could show example.com but really be loaded from Google'S A
by ericflo 9y ago
I don't understand. So now the URL bar won't always show where the page was actually loaded from? It could show example.com but really be loaded from Google'S AMP servers? If I'm reading this right, I find it very sad.
- cramforce 9y agoWeb Packaging [https://github.com/WICG/webpackage https://github.com/WICG/webpackage] allows the authority over an origin to delegate serving to a third party (and support things like offline serving). This is similar, but better than e.g. what a CDN does today, because the third party does not need access to the private key.
- wmf 9y agoThat's how CDNs already work. For example, apple.com is served from Akamai. And AMP is planning to use cryptographic signing so that the browser can verify that the CDN didn't tamper with the page.
- jopsen 9y agoWell, today Apple is trust Akamai with a certificate for their origin: apple.com In this future, it seems like the content will be signed with Apples TLS certificate/key and then the content can be distributed by anyone. This could open the doors for a more distributed web too :)
- ericflo 9y agoTo be honest, the more that I've looked into this, the more it seems like a good idea. It was not presented as a new and fairly dramatically different way of distributing content on the web, it was presented as a way to get around showing the URL in response to pushback from the web community. I think if this announcement were written differently, I would've come away with a much better impression of the whole thing.
- jopsen 9y agoYeah, the AMP thing just seems like a nice use-case... But the new door this opens in terms of content distribution are very interesting. Shared caches might be a thing again... Who knows :)