Humans can't read URLs. How can we fix it?

#1

Post by asdf-asdf-asdf » Tue, Jan 28, 2020, 6:22 PM UTC

Humans can't read URLs. How can we fix it?
youtube.com

Re: Humans can't read URLs. How can we fix it?

#2

Post by dfabulich » Tue, Jan 28, 2020, 7:36 PM UTC

In this video, a Googler here proposes adding the "ETLD+1" part of the domain name as a "chip" where the extended-validation certificate name used to be.

So this link: https://jakearchibald.github.io/svgomg/

Would look like this in the browser:

    jakearchibald.github.io | https://jakearchibald.github.io/svgomg/

The proposal appears at 16:45 https://www.youtube.com/watch?v=0-wB1VY3Nrc&t=16m41s

Re: Humans can't read URLs. How can we fix it?

#3

Post by jaffathecake » Wed, Jan 29, 2020, 11:20 AM UTC

dfabulich wrote: post #2

In this video, a Googler here proposes adding the "ETLD+1" part of the domain name as a "chip" where the extended-validation certificate name used to be. So this link: https://jakearchibald.github.io/svgomg/ Would look like this in the browser: jakearchibald.github.io | https://jakearchibald.github.io/svgomg/ The proposal appears at 16:45 https://www.youtube.com/watch?v=0-wB1VY3Nrc&t=16m41s

More specifically, https://workforus.theguardian.com/index.php/careers/ would look like this:

     theguardian.com | workforus.theguardian.com/index.php/careers/