Note: Personally URLS should be backwards to make sense.. com.google.mail/sub/folder (go in order of largest authority down to the smallest subfolder).
At the moments it's
Note: Personally URLS should be backwards to make sense.. com.google.mail/sub/folder (go in order of largest authority down to the smallest subfolder).
At the moments it's
And com.google.mail would mean specifying the least meaningful information first. Would you rather be introduced to someone as "Widgets Incorporated, Director of Widgets, John Doe" or "John Doe, Director of Widgets at Widgets Incorporated".
"Okay, the domain in the URL for this link is X, but I know my bank's domain is Y, therefore it's a scam."
Part of it is the URL syntax being unintuitive, part of it is simple lack of proper education/training. But it seems like in the time you tell people "DON'T CLICK LINKS IN EMAIL OMG", you could just teach them how to read a URL.
Maybe if URLs had spaces and looked a little more like a postal address than a confusing jumble, people might actually read them. As it stands now, though, most people just type everything into a search page -- even if they're actually typing in a URL as a search term. Kind of like that story about the number one search term on MSN being Google.
http://(com,google,mail,)/sub/folder
The parentheses and commas make it absolutely clear that you're dealing with a reordered URI-authority-component.
Even the trailing comma and off-paren are significant in our most common use-case: determining whether a URI falls within a certain hierarchical collection-scope by making a simple prefix-comparison. Compare the prefixes:
The first would also accept < http://(com,googlepages, > URIs, while the second would accept all subdomains of < com,google, >, and the third accepts only URIs strictly on < com,google, > but not its subdomains.