3 ms·

What's wrong with bolding or otherwise emphasizing the TLD plus one more level of the domain? I wouldn't even mind (I would, but I'd get used to it) the url ba

What's wrong with bolding or otherwise emphasizing the TLD plus one more level of the domain? I wouldn't even mind (I would, but I'd get used to it) the url bar showing com.ycombinator.news/item?id=7694967 to avoid super long subdomains obscuring the main domain. But forcing a click to show the full uri? That's going to eat up a lot of aggregate developer time. It also does nothing to address a major problem: companies using alternate domains for their services. It does me no good to know what the real domain is without any other distracting information, if I can't tell whether than real domain is trustworthy. The browser would have to maintain a map of trusted organizations and domains they're known to use, and show the trusted official domain in place of other domains. Which is problematic for several reasons (not the least is the effort required to maintain such a list), and could lead to additional security problems in edge cases (domains transferred to new owners, etc).

couchand 12y ago
It sounds like you're describing SSL certificates.
plorg 12y ago
I suppose this is somewhat off-topic, but confusion of TLDs reminded me of the following story: When I was still using a dumbphone I figured out that AT&T would let me sync my contacts to the web. I figured I'd try to do that to see if I could make them more manageable (by not having to edit them on a tiny screen with T9). I searched all over the AT&T account page (att.com - where I view and pay my bills) and couldn't figure out how to access my contacts on the website. Eventually I googled enough to find out that I needed to manage contacts through att.net. That website redirected to a Yahoo page (att.yahoo.net) which didn't take the same credentials as att.com (that is, the att.com user:pass did not work), but if one was signed into the dot.com they could automatically be logged into the dot.net. It's extremely confusing. Once logged in, I was presented with an interactive flash or heavy javascript page which, if not for the .csv import/export feature, I would find much more cumbersome than even just using the phone. Before I managed to get logged in I clicked on numerous pages that redirected me to att.yahoo.net. Because it is labeled (and decorated) as a Yahoo webpage (and is, I assume, operated by Yahoo), I was quite confused over what credentials to use and if I was in fact at the proper website.

couchand 12y ago

It sounds like you're describing SSL certificates.

plorg 12y ago

I suppose this is somewhat off-topic, but confusion of TLDs reminded me of the following story: When I was still using a dumbphone I figured out that AT&T would let me sync my contacts to the web. I figured I'd try to do that to see if I could make them more manageable (by not having to edit them on a tiny screen with T9). I searched all over the AT&T account page (att.com - where I view and pay my bills) and couldn't figure out how to access my contacts on the website. Eventually I googled enough to find out that I needed to manage contacts through att.net. That website redirected to a Yahoo page (att.yahoo.net) which didn't take the same credentials as att.com (that is, the att.com user:pass did not work), but if one was signed into the dot.com they could automatically be logged into the dot.net. It's extremely confusing. Once logged in, I was presented with an interactive flash or heavy javascript page which, if not for the .csv import/export feature, I would find much more cumbersome than even just using the phone. Before I managed to get logged in I clicked on numerous pages that redirected me to att.yahoo.net. Because it is labeled (and decorated) as a Yahoo webpage (and is, I assume, operated by Yahoo), I was quite confused over what credentials to use and if I was in fact at the proper website.