Live data from Hacker News

Chrome hides www and https:// in the address bar again

bleepingcomputer.com

41–50 of 194 posts

Re: Chrome hides www and https:// in the address bar again

#41
post #6

URLs represent and identify content,controling them means you control content. In the short term these changes mean little but in the long term this will benefit google immensely. Google just loves slippery slopes. Identity and payment are extremely important to any ordered system of social interaction. More than content itself,controlling them helps one control everything else. I am trying hard to avoid believing co…

Legally requiring internet standards compliance would help in some ways, but imagine the hurdle that creates for future startups who have something different and maybe better in mind

Re: Chrome hides www and https:// in the address bar again

#42
This behavior will train users to believe that the www in domains isn't important, when it actually serves a very important purpose.

You can't cname example.org, which makes it very hard to use a CDN to serve it unless the CDN provides anycast ips or you delegate DNS to the CDN.

If they're intent on making the address bar useless, they may as well go full hog, like Apple does in desktop Safari -- the address bar shows the domain only, until you click.

Re: Chrome hides www and https:// in the address bar again

#43
post #38

This reminds me of how Windows frustratingly hides file extensions by default. This sounds low-upside/high-downside to me, but it's the sort of thing with simple arguments-for (easier for clueless users! Cleaner!), and nuanced arguments-against (eliding rarely-useful details in special cases causes ambiguity, and can lead to confusion is some cases, particularly for clueless users).

And, there is a setting to tell it to not do that, but even then, for some files it is hidden anyways. But, it is possible to use regedit to change it so that the extensions are not hidden even for those cases.

Re: Chrome hides www and https:// in the address bar again

#44
post #42

This behavior will train users to believe that the www in domains isn't important, when it actually serves a very important purpose. You can't cname example.org, which makes it very hard to use a CDN to serve it unless the CDN provides anycast ips or you delegate DNS to the CDN. If they're intent on making the address bar useless, they may as well go full hog, like Apple does in desktop Safari -- the address bar show…

But it’s definitely not important for an average user typing “facebook.com” into the address bar. Safari proved that.

Re: Chrome hides www and https:// in the address bar again

#45
post #38

This reminds me of how Windows frustratingly hides file extensions by default. This sounds low-upside/high-downside to me, but it's the sort of thing with simple arguments-for (easier for clueless users! Cleaner!), and nuanced arguments-against (eliding rarely-useful details in special cases causes ambiguity, and can lead to confusion is some cases, particularly for clueless users).

Finder on macOS does this too. It's maddening...

There was an article recently about "hostile architecture" and this is similarly a "hostile software design" to prevent users from doing something the developers don't want them to do.

Re: Chrome hides www and https:// in the address bar again

#46

This is great and all until you (like me) need to be able to differentiate www.example.com from example.com and https:// example.com versus http:// example.com. My website doesn't forward example.com to www.example.com (due to errors on my part that I don't know how to fix, my email is in my profile and if you can help I'd greatly appreciate it). I don't know if there are any scenarios in which a properly-configured…

Can you just set a CNAME record in your DNS settings for that redirect?

Re: Chrome hides www and https:// in the address bar again

#48
post #38

This reminds me of how Windows frustratingly hides file extensions by default. This sounds low-upside/high-downside to me, but it's the sort of thing with simple arguments-for (easier for clueless users! Cleaner!), and nuanced arguments-against (eliding rarely-useful details in special cases causes ambiguity, and can lead to confusion is some cases, particularly for clueless users).

And, there is a setting to tell it to not do that, but even then, for some files it is hidden anyways. But, it is possible to use regedit to change it so that the extensions are not hidden even for those cases.

Editing Chrome flags is similar to editing the Windows registry. Here are the relevant settings:

chrome://flags/#omnibox-ui-hide-steady-state-url-scheme

chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains

chrome://flags/#omnibox-ui-hide-steady-state-url-path-query-and-ref

Re: Chrome hides www and https:// in the address bar again

#49
post #6

URLs represent and identify content,controling them means you control content. In the short term these changes mean little but in the long term this will benefit google immensely. Google just loves slippery slopes. Identity and payment are extremely important to any ordered system of social interaction. More than content itself,controlling them helps one control everything else. I am trying hard to avoid believing co…

Legally requiring internet standards compliance would help in some ways, but imagine the hurdle that creates for future startups who have something different and maybe better in mind

Well, claiming that it is compliant even though it isn't, is false advertising, so that is how it should be applied, rather than requiring compliance even for the thing that isn't supposed to be. They already require warning labels on some stuff, so it should be required that warning label too, then, maybe.

Re: Chrome hides www and https:// in the address bar again

#50
post #28

What a slippery slope. I imagine a future when the entire URL itself has disappeared and we live in some sort of Google-controlled walled garden environment, like what they're trying to do with AMP[0]. Some sites only work with WWW prefixed as the APEX DNS record is misconfigured and points to nothing. I've even seen some sites point to `0.0.0.0' but had a CNAME record for WWW and I could then view the site. [0] http…

Then these websites are broken and needs to be fixed. In the end, the most of the people would probably search for it in the first place.
Post reply on HN