URLs can be complex and sometimes not intended for human consumption. So fine, don't display the URL. Define a full-on standard that lets a user agent show a

URLs can be complex and sometimes not intended for human consumption. So fine, don't display the URL. Define a full-on standard that lets a user agent show a "friendly but not unwieldy" name to the user. You have that funky Graph API or whatever Facebook started to allow URL posts in Facebook to expand to include site info. Why not just use that at the top of browse? Then design the browser to allow access and editing of the URL somehow if desired (an old browser called 'OB1' didn't display the URL unless you pressed Ctrl-W, for example), but don't display it by default. The truth is probably not many technical people directly enter URLs in browsers any more. Honestly maybe it wasn't a good idea to allow query strings in URLs. Perhaps deprecate them and keep URLs looking like hierarchical filenames. Which honestly, is still something difficult to understand for non-technical people. But this crap of hiding parts of it is dumb.