701–710 of 919 posts
Earlier quoted context omitted.
Ehh this might have been true 10+ years ago, but most people are more savvy than that today.. I think you are describing something that is less and less common (which may explain why Google is trying to encourage people to keep doing it).
You'd be really surprised. There are still people that do exactly what the grandparent comment relates, today, in 2018.
Earlier quoted context omitted.
Some engines have two per cylinder :)
I find this interesting. The parallels up to this point. My intent is not to pick fun on anyone but to just relook at the conversation just had. We're talking about users not understanding the technology they use daily. jwalton, in trying to give an example with spark plugs, allowed a more knowledgeable user or practitioner, mirimir, to give a more technically-correct description. It seems to echo the main problem we…
But it's arguably not such a great example, because details of engine design are generally trivial for drivers. Maybe a better example is the low oil pressure indicator. Maybe most people don't know what that actually means, but not having one can lead to severe engine damage. Years ago, I had a car with an oil radiator, and the oil line failed. So I knew to stop immediately.
Considering 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…
Google knows best, DNS standards be damned. Practice makes standard. /s
Considering 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…
This and many other changes over a course of a short period of time have caused me to go to Firefox exclusively now. I heard Firefox is going to stop third party cookie tracking altogether. Why not give Google the big finger and use a different browser? Vote with your cold hard actions if you feel so strongly about something.
Firefox is a better browser due to tree style tabs. But it is noticeably slower.
Regardless of FF's little quirks, I use it almost exclusively for personal stuff. I would rather deal with those types of things than the mentality Chrome brings to table.
Earlier quoted context omitted.
What you may be surprised to learn is that Chrome isn't just stripping "www." from the beginning of the subdomain. "subdomain.www.domain.com" displays as "subdomain.domain.com"
I just downloaded canary and tried it and you are absolutely right. about.www.github.io shows as about.github.io I'm on board with this change in general, but this is absolutely something that needs to be fixed. Not only is that just annoying and wrong, but it could be dangerous in some situations. Also, it doesn't just stop at one removal. http://www.www.about.www.www.stuff.www.www.example.com shows as about.stuff.e…
I'm ok with hiding "www.", but it also hides "m." which is sometimes very confusing (I once opened a m.facebook.com link and was very puzzled why it uses the mobile site when the URl bar just shows "facebook.com").
This and many other changes over a course of a short period of time have caused me to go to Firefox exclusively now. I heard Firefox is going to stop third party cookie tracking altogether. Why not give Google the big finger and use a different browser? Vote with your cold hard actions if you feel so strongly about something.
Safari already hides "www.". In fact it hides everything except the root-level domain, e.g. " https://www.google.com/about/" shows just "[lock] google.com". Firefox and Opera show the full domain but gray out everything in the entire URL except the root-level domain, so "www." is gray. Just saying, de-emphasizing and hiding parts of the URL is clearly a trend. This isn't just a Google thing.
De-emphasizing is fine, hiding alltogether is not -- for both protocols and subdomains.
amazon.de is visible on focus it's https://www.amazon.de
URL's is already dead.