It makes a lot of sense to me to redesign how we display URLs. Right now, we show them as a singular identifier, where the only thing we can tell the user is to

It makes a lot of sense to me to redesign how we display URLs. Right now, we show them as a singular identifier, where the only thing we can tell the user is to search for things inside that string of characters (look for https, or look for bankname.com). We don't need to show the whole string of characters. It seems very sensible to me to take the URL for what it is and communicate that back to the user: - The protocol doesn't matter much to most people, except the implications it has, so maybe show "encrypted" or "not encrypted" (and fallback to protocol name for FTP and the like, most people won't ever touch that without knowing what it is) - The domain is interesting: there's the TLD, which doesn't _really_ matter, and the second level name, which matters a lot. Subdomains matter less. How about we show it as a much more prominent "[ domain.com ]" with a less obvious subdomain. - Paths are pretty generic all around: incrementally deeper descriptors separated by forward slashes. Could definitely show that as a breadcrumbs-style thing (might also make people care more about readable paths, which is nice). - The query string should probably be shown as "tags" with a key and value, since that's what they are. - The hash is a bit icky, but it might be enough to highlight that you're linking to a place in the page. Could be displayed as something like this: https://i.imgur.com/RfJoP23.png https://i.imgur.com/RfJoP23.png