Chrome for Developers
3 HN recommenders · recommended in 5 months, 2020–2023
20:21 · 59K views · Jan 28, 2020
Jake Archibald argues that URLs are nearly impossible for humans to interpret, especially for security. He walks through what browsers do about it, including highlighting the registrable domain, and floats a possible better design.
Referenced in debates over Chrome hiding URLs as a compelling case for why full URLs are hard even for experts.
7 comments from Hacker News
Reading URLs is actually really hard - even for experts. This video covers the problems well: this video This is bad for web security, since the registerable domain is the part you have to trust, but it's surprisingly difficult to figure out that part. However I feel a bit uneasy about this since URLs are important and tell you where you are on a website. I prefer Firefox's approach which emphasises the registerable domain in the URL bar and fades out the rest of it, making it easier to spot the important bit. However it's still quite subtle - it could do with being a clearer distinction.
A couple of Google Chrome devs talk about the issues surrounding the readability of urls and their security implications and possible solutions in an episode of their podcast[0]. I think they make a compelling argument for hiding most of the url in part to prevent phishing however I do think they should allow this behaviour to be toggled via a flag. [0] this video
Jake Archibald (a Googler) presents some decent points on this on the HTTP 203 podcast: this video I still don't agree with the removal of URLs, but I do still recommend watching the entire video if you want to get more perspective on the issue (beyond just the conspiracy theories about AMP and control).
Why did Google select someone unknown to announce this? It's also the second time I've noticed Google had someone the UK introduce an unpopular proposal to Chrome. The other one was removing the URL from the address bar (accusing the author of You Don't Know JS of being "Trump-like" for how he disagreed with him in the process). this video [LINK] [LINK] Is there a special ops team? Of the FAAMGs my favorite is Google, but this makes me reconsider my position.
In this video, a Googler here proposes adding the "ETLD+1" part of the domain name as a "chip" where the extended-validation certificate name used to be. So this link: [LINK] Would look like this in the browser: jakearchibald.github.io | [LINK] The proposal appears at 16:45 this video