Humans can't read URLs. How can we fix it? - HTTP 203

Channel:Chrome for Developers · Length:20:20 · Published:2020-01-28 · Views:59242

Watch on YouTube

Summary

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.

Why HN recommends it

Referenced in debates over Chrome hiding URLs as a compelling case for why full URLs are hard even for experts.

I think they make a compelling argument for hiding most of the url in part to prevent phishing — HN, 2020

Web development · Security & hacking · UX & UI design

Subtitles (excerpt)

JAKE: All right. I'm switching back to my broadcast voice. I'm ready to go. SURMA: [BABBLING] JAKE: You're not. It's almost like I stole your ability to speak there. [LAUGHTER] But that's fine. It's my episode. You can just listen to me talk. SURMA: All right. Let's do it. JAKE: Yeah, excellent. SURMA: I'm just going to sit here and watch. [MUSIC PLAYING] JAKE: I've been thinking about URLs. There's one. SURMA: On your own blog, as always. [INTERPOSING VOICES] JAKE: I've got to advertise my blog. I haven't done anything in 2020 yet. But you know, it's a URL. Every now and then, there'll be a Twitter thing that goes round about Chrome changing URLs or something. SURMA: No. Killing. JAKE: Killing URLs is-- SURMA: We're killing URLs. JAKE: --another way it's put. And everyone's angry about it. So I kind of wanted to just condense some of my thinking about URLs. Hopefully, it won't be too controversial. It might be a little controversial. SURMA: Let's see. The comments will let us know. JAKE: URLs, what are they? They are like a serialization of a request. Yeah? Does that make sense? SURMA: Part of it. JAKE: Part of it, and that is absolutely a good point. But I can give you this string.

On Hacker News

Jake Archibald (a Googler) presents some decent points on this on the HTTP 203 podcast: [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). — davidmurdoch, 2020-08
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] [VIDEO] — Orochikaku, 2020-06
Reading URLs is actually really hard - even for experts. This video covers the problems well: [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… — AshleysBrain, 2020-06
Yes. Years. I think a URL bar that sticks to the security relevent parts is a good idea. It's hard for even experienced users to figure that stuff out. I tried to explain it here [VIDEO] — jaffathecake, 2021-06
It is, there’s a long special list for domains that host arbitrary subdomains, GitHub pages is one of them. It’s explained well in [VIDEO] — felixfbecker, 2020-06

Related videos