Chrome 69: “www.” subdomain missing from URL
621–630 of 919 posts
Re: Chrome 69: “www.” subdomain missing from URL
#622Considering a subdomain "trivial" is ridiculous... there's a difference between "www.example.com" and "example.com". Not only can they serve different sites, they can even have different DNS records! It seems that "m." is also considered a trivial subdomain. So when a user clicks a link to a "m.facebook.com" uri, they'll be confused why FB looks different when the browser reports it's on "facebook.com". I sincerely h…
Re: Chrome 69: “www.” subdomain missing from URL
#623> 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…
If you care about usability this is clearly an improvement. The cost/benefit doesn't work out. It's a usability improvement, but it comes with a huge cost, where many, many sites have the fundamental function of a URL -- that of an address/specifier across the internet -- basically broken. The person who implemented this change either didn't work out the cost, or decided they didn't care. Everyone is hyperventilating…
If they replaced the country code with a flag, that would be an improvement. If they replaced the carrier number with the logo of the company that's also not bad. These are UI changes and the one you proposed about the phone numbers are great :)
Re: Chrome 69: “www.” subdomain missing from URL
#624Earlier quoted context omitted.
Why not drop .com then as well? Most sites are on .com domains after all. It is exactly the same issue. A domain is a domain. Google is arbitrarily dictating your CNAME from the user's perspective. What if you don't serve your site off of mysite.com is google going to automatically try again at www.mysite.com? What if you have distinct content at both domains? This decision is stupid.
> Most sites are on .com domains after all. Most sites in English , and even that is doubtful. There's a full world out there of people and businesses using ccTLD like .fr, .nl, .co.uk, .hr, .rs, .es, .jp...
Of the TDL you mention the top one is .jp at less than 2%. If you remove the qualifier under the .uk TLD you get an additional 2%. The rest don't make the chart.
https://www.statista.com/statistics/265677/number-of-interne...
Re: Chrome 69: “www.” subdomain missing from URL
#625Earlier quoted context omitted.
i use Firefox @ work and @home for serious stuff. The only reason i don't use Firefox 100% is due to the Android app which is a lag fest. Mozilla needs to put more resources on Android.
I'm in the opposite boat from you. Firefox on Android is nice, especially thanks to being able to install an ad blocker. Firefox on my desktop literally brings my entire machine to its knees, and destroys performance in all other apps that are open. Pulling that off while not even getting close to maxing out the CPU is rather impressive. :/
Re: Chrome 69: “www.” subdomain missing from URL
#626Re: Chrome 69: “www.” subdomain missing from URL
#627Re: Chrome 69: “www.” subdomain missing from URL
#628Earlier quoted context omitted.
But why add to the confusion by hiding important information?
If in most uses minds, "www.example.com" is the same as "example.com", then "example.com" is less confusing because they have probably never heard of the word "subdomain".
Perhaps they should be taught.
Otherwise let's move on to making nuclear reactors less confusing.
Re: Chrome 69: “www.” subdomain missing from URL
#629Earlier quoted context omitted.
Oh come on. "www." was used as a way of delineating what was a web address. Hence the fashion of putting that there so people knew you had to do it in the browser. Before then people used to also put the " http://" on there, and the combination of the two on vehicles/signs was ridiculous. We're now in a web world. People know what a URL is. "domain.com" isn't ambiguous, it's obvious to man, beast or child that you ty…
There is an actual (small) reason for the existence of "www" nowadays. You cannot have a CNAME record for the domain apex (example.com). Many dns providers implement a workaround by resolving the CNAME record into A/AAAA records when queried. https://serverfault.com/questions/613829/why-cant-a-cname-re...
Re: Chrome 69: “www.” subdomain missing from URL
#630Earlier quoted context omitted.
Oh come on. "www." was used as a way of delineating what was a web address. Hence the fashion of putting that there so people knew you had to do it in the browser. Before then people used to also put the " http://" on there, and the combination of the two on vehicles/signs was ridiculous. We're now in a web world. People know what a URL is. "domain.com" isn't ambiguous, it's obvious to man, beast or child that you ty…
How about older people? Can your parents explain the difference? Mine can't and I can assure you most of them are the same.
Grandma: I'm typing domain.com into my browse on [random device] and it doesn't work.
Nerd grandchild: well that's because it doesn't exist.
Grandma: But it works on my other computer.
Nerd grandchild: that's because the browser tries lots of domains like www.domain, domain.org and so on when you enter domain.
Grandma: yes, I noticed that. When I enter www.domain.com, it automatically corrects it to domain.com. So that's must be the right one, surely?
Nerd grandchild: Nope. domain.com is the correct domain. It's just trying not to confuse you.
Grandma: ?