3 ms·
I could see some sort of alternative URL bar ("https://nyt.com/somearticle/ https://nyt.com/somearticle/ | served by https://somecdn.example.org/blah" https://s
by jml7c5 6y ago
I could see some sort of alternative URL bar ("https://nyt.com/somearticle/ https://nyt.com/somearticle/ | served by https://somecdn.example.org/blah" https://somecdn.example.org/blah"), but complete replacement is far too dangerous and confusing in that it is completely hidden.
- jefftk 6y agoThe New York Times surely already serves their pages through a CDN, silently, and with the CDN having the full technical capability to modify the pages arbitrarily. Signed exchange allows anyone to serve pages, without the ability to modify them in any way. (Disclosure: I work for Google, speaking only for myself)
- jml7c5 6y agoMy objection is that it's no longer clear if you're dealing with content addressing or server addressing. If I see example.com in the URL bar, is it a server pointed from the DNS record example.com (a CDN that server tells me to visit), or am I seeing content from example.com? If I click a link and it doesn't load, is it because example.com is suddenly down, or has it been down this whole time? Is the example.com server slow, or is the cache slow? Am I seeing the most recent version of this content from example.com, or did the cache miss an update?
- KajMagnus 6y agoWhat if there was a `publisher://...` or `content-from://...` or `content://...` protocol, somehow? (visible in the address bar, maybe a different icon too, so one would know wasn't normal https:) And by hovering, or one-clicking, a popup could show both the distributor's address (say, CloudFlare), and the content's/publisher's address (say, NyT)?