|
|
|
|
|
|
by lugg
2879 days ago
|
|
|
Chrome already handles this: if you want the domain enter in the protocol - https:// If you want to search leave it off. On top of that Chrome already has the ability to redirect you straight to the domain if it is well defined. I can't imagine it difficult to move that logic to google redirects instead. e.g. "test.vm" goes to a google search despite being url format. "test.dev" goes to domain. |
|
|
"I'll prefix the domain with https:// so I will directly establish a secure connection because leaving it out implicitly means plain http, which makes me vulnerable to mitm attacks" - nobody outside tech, ever
And it wouldn't be any different here. Over the last decade we've been so focused on dumbing down tech enough so that it's accessible to pretty much anyone on the planet. It will be very hard to reverse this trend. Even just adding a trailing slash is cumbersome. I can only imagine how many million man hours we'd have to waste worldwide to explain that to the average Joe and their mom. Just remembering how many times I've seen people type a backslash instead of a slash in URLs, this will be fun.