Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

401–410 of 919 posts

Re: Chrome 69: “www.” subdomain missing from URL

#401

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

Yes, this point is important. We need to get the web/internet as simple as changing channels on a television. That is what the masses are capable of.

Re: Chrome 69: “www.” subdomain missing from URL

#402
This is the third story today about a Google's handling/intentions towards web addresses and general webpages. The theme is Google wants/may want to push a new set of Google orientated web standards. This seems the least likely of the three to be strategically related,however.

The other two: Google may/may not be pushing the open web standard towards their own AMP pages, instead:

https://news.ycombinator.com/item?id=17920720

Google wants to get rid of URLs but doesn't know what to replace it with:

https://news.ycombinator.com/item?id=17925761

Re: Chrome 69: “www.” subdomain missing from URL

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

Re: Chrome 69: “www.” subdomain missing from URL

#404

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

How is this a usability improvement? What are the positives I'm not seeing?

Re: Chrome 69: “www.” subdomain missing from URL

#405
post #389

Earlier quoted context omitted.

The reason why Google is doing this is because they are slowly trying to do away with URLs, as direct traffic is probably their greatest untapped segment. Google is trying to get users to go through their doorway pages, which is exactly the kind of thing for which they penalize publishers. Pay attention to when you enter direct addresses, let's say from a device/media subscription authorization page. The autosuggesti…

Sorry, what? Could you expand on this? What do you mean by doing away with URLs?

Many users never use the url bar. They just 'Google' for websites they want to access and follow the results.

Re: Chrome 69: “www.” subdomain missing from URL

#406

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

Yes, this point is important. We need to get the web/internet as simple as changing channels on a television. That is what the masses are capable of.

How does hiding part of the domain make the web any easier to use?

Re: Chrome 69: “www.” subdomain missing from URL

#407
post #396

> This is a dumb change. No part of a domain should be considered "trivial". As an ISP, we often have to go to great lengths to teach users that "www.domain.com" and "domain.com" are two different domains... What ISPs teach their users anymore these days? Why the heck do we want to go back to that? Time for a modicum of historical perspective. If you care about usability this is clearly an improvement. This is part o…

Two prominent examples noted in the bug: https://citibank.com.sg and https://www.citibank.com.sg are different, http://www.pool.ntp.org and http://pool.ntp.org are different. Like, big companies run separate servers on the two domains. That's besides the fact where if you have www.example.www.example.com, it rewrites to example.example.com.

The first citibank url doesn’t load for me, so it is site vs not site rather than two different sites, and both those ntp urls are redirecting me to https://www.ntppool.org/en/ - perhaps there’s less substance than meets the eye to those complaints.

Re: Chrome 69: “www.” subdomain missing from URL

#408

Earlier quoted context omitted.

What if you visually copy and paste? Parent is right.

One more reason to set up a redirect from or to www.

Many MANY legacy sites serve different information at those two domains.

Re: Chrome 69: “www.” subdomain missing from URL

#410
post #12

Yo, this is... going too far, c'mon now. While sure, www seems odd now, it's still a subdomain and we're inching into territory of obscuring things that matter for small gains in end-user perception that aren't _that_ impactful.

This is not only obscuring. This is plain breaking tons of stuff for people.

Can I ask what's broken? I understand it's displayed incorrectly in the worst cases and obscurely in most, but broken?
Post reply on HN