Google resumes its attack on the URL bar, hides full addresses on Chrome 86

Re:Google resumes its attack on the URL bar, hides full addr... by RonanTheGrey on Friday August 14, 2020 @02:35PM (#24161570)

All of which can be done without AMP, hiding the url, or forcing companies to use it or lose their SEO placements.

It's the SUM of the pieces that point to Google's endgame, not the individual pieces themselves.

I have an idea.

Move forward with signed exchanges, and then prohibit them from being used to obscure the content source (more specifically, require the 3rd party to reveal themselves)

[ Parent | on HN ]

Re:Google resumes its attack on the URL bar, hides full addr... by Spivak on Friday August 14, 2020 @04:21PM (#24162774)

I mean I don't disagree with you that I should be able to look and see what entity actually served me the content in the same way I can see who signed the sites SSL cert but I'm still 100% in favor of having browsers present display the bundle's URL in the browser because that's the site your viewing.

A site that uses Cloudflare as a CDN isn't cloudflare.com/site/nyt.com. The whole point of these things is that if you have some vested interest in being a CDN for chunks of the web for your users you don't have to set up a partnership with them and proxy their site or have their certs you just download the bundle and go.

I detest AMP, but I'm very much looking forward to signed exchanges.

[ Parent | on HN ]