Live data from Hacker News

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

bleepingcomputer.com

51–60 of 194 posts

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

#52

Can someone help me understand why this is a big deal? Safari has had this change for a while and I haven't felt like I'm missing anything. Where's the slippery slope? Does have to do with AMP?

It has nothing to do with AMP. There's a lot of reasons why, but one reason is for example, two different sites can technically be hosted on www. and the non-www version, if the site isn't set up to redirect the www to the non-www, for example. So this could, in certain scenarios, pose a security risk in that if you pretend that www and the non www are the same sites -- when they're not -- it can make it easier for those that hijack one or the other to get away with it. Now, that's fairly extreme and esoteric. But there are actually times in development when you use subdomains, which this makes more difficult, and there's other subdomains they're considering trivial which, in fact, aren't. This is really good discussion on the topic and why this change just simply ignores so many technical issues, best practices and simply realities: https://bugs.chromium.org/p/chromium/issues/detail?id=881410

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

#53
post #21

Off topic : there seems to be a disconnect between the chrome devs and users. Another instance was the automatic signing in to chrome incident. I've lost trust in the chrome team and have switched to Firefox full time and honestly there's nothing that I miss. The firefox devs seem to better understand their users, frequently blog about changes that positively impact users. I have a lot more faith in firefox even thou…

I think the chrome team just considers its users to be your average corporate america employee, and no longer considers developers or tech literate people to be their main market.

I doubt that, because the number of times they completely ruin chrome as an intranet browser in the last few years with TLS handling, self signed cert handling, and general settings window changing malarkey shows that they are not even catering to that market very well, especially when they add a workaround and take it away in a very short window which for better or worse is often much shorter than most large organization's change control windows. Firefox generally keeps most workarounds working for as long as I've needed to worry about it, but Chrome's timelines seem arbitrary and the UI changes make keeping Chrome configuration guides a constant churn.

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

#54
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…

The focus of this change is to improve the identification of content. This coupled with payment has been subject lots of fraud where users misled about the owner of a website. google-payments-secure.via.net is not a google payment website despite the google in the domain name. The key part that signifies the ownership / identify of the person hosting the site is the END of the domain, the google.com part. That is the…

There are other ways to do this that do not hide parts of the URL.

Educating people should not hide information, but instead present information in a way that is more understandable. I think the Chrone team is making URLs harder to understand.

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

#55
I would have no trouble with hiding "https://" in the address bar, as long they show it for other protocols (including http). It might help move us to a world with https everywhere even faster.

I still prefer Firefox: protocol, subdomains and path are greyed out but still clearly legible. This way I can eyeball "on which site am I?" quickly (and read google-secure-payments.google.via.net as via.net for example) and still have access to the full URL in 0 clicks.

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

#56
post #9

Earlier quoted context omitted.

my chrome hasn't updated yet, but my understanding of this change was that you could display the full unmolested URL by simply clicking in the address bar. is that not the case?

double clicking. but still.

Wow, that is mad. So glad I switched to Firefox.

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

#57
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.

If the url isn't important enough to display, then they shouldn't display it. They can display just the domain. They shouldn't display almost the url, but they removed an important thing.

Edit to add: if you type in an almost url from the screen or a screenshot, it's likely to not take you to the same page, and you'll be confused as to why. If you type in the domain only and go to the home page, that's not that confusing.

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

#59
post #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.

And requires you to jump through non-obvious hoops to make "hidden" files and folders visible.
Post reply on HN