4 ms·
Reading URLs is actually really hard - even for experts. This video covers the problems well: https://www.youtube.com/watch?v=0-wB1VY3Nrc https://www.youtube.co
by AshleysBrain 6y ago
Reading URLs is actually really hard - even for experts. This video covers the problems well: https://www.youtube.com/watch?v=0-wB1VY3Nrc https://www.youtube.com/watch?v=0-wB1VY3Nrc
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.
- anewdirection 6y agoIs this a parody comment?
- Lammy 6y agoThe way we use DNS (reversed) does make URLs kind of confusing for specificity, like: https://specific.more.less.example.com/less/more/specific.html https://specific.more.less.example.com/less/more/specific.ht...
- AshleysBrain 6y agoThe video points out things like: how do you spot an eTLD? There's .com, but what about .co.uk? .github.io? Do you know all the exceptions? There's basically a database of them and you just have to know them to correctly interpret the security origin of the domain.