31–40 of 194 posts
If I have one webpage with different languages and want my visitors recognize it from url, what are the options? Previously I could have www.example.com/en/ and www.example.com/fr/ etc If subdomains are not possible there's no hope that visitors using Chrome would see it?
Subdomains in general still show, just not www. Also, in the case you mentioned, the subdomains are the same. The path still shows.
Google wants nobody to know URLs exist, and that everyone is forced to search Google for everything, even sites they know, and there visit fake AMP-sites portraying to be from a server they are not, all while Google tracks every single keystroke you make. This is just another tiny step in that overall plan, and it is 100% evil. Don’t waste your time trying to talk the Chrome-team into reason. You are not their custom…
Google wants nobody to know URLs exist, and that everyone is forced to search Google for everything, even sites they know, and there visit fake AMP-sites portraying to be from a server they are not, all while Google tracks every single keystroke you make. This is just another tiny step in that overall plan, and it is 100% evil. Don’t waste your time trying to talk the Chrome-team into reason. You are not their custom…
yeah, if you don't like this change switch to a browser that has behaved this way for years
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…
Brave ( https://brave.com/download/ ) is a good alternative too. It doesn't have the terrible UX (IMHO) that Firefox has. But it is built with Chromium (TMK).
I'm certainly not a fan of the new URI scheme, but it is worth pointing out that Safari has already made the same change. Furthermore I'm not convinced said change is a net-negative for the average consumer. Safari added the setting "Show full website address", which does just that. I wouldn't have a problem if Chrome followed suit and defaulted to the new scheme, but gave us the option to show the full URI.
Safari only shows the domain name. Chrome still shows both the domain name (minus "www.") and URL path.
Google wants nobody to know URLs exist, and that everyone is forced to search Google for everything, even sites they know, and there visit fake AMP-sites portraying to be from a server they are not, all while Google tracks every single keystroke you make. This is just another tiny step in that overall plan, and it is 100% evil. Don’t waste your time trying to talk the Chrome-team into reason. You are not their custom…
Firefox and Safari already made similar changes. Safari made the exact same change, and Firefox hides http:// already, but not https:// , chrome is just using a lock icon to represent the https:// instead of the actual string.
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 don't like the change either, for a variety of reasons, but I don't think I'm their average user either. For the average user, seeing the domain and nothing else likely improves security.
Google must really hate URLs. My search results recently stopped showing the full path of the URL, just the domain name. It was a huge pain because I was looking for an item at Ikea and couldn't tell if a result went to their American site or to their UK, Saudi Arabian, Qatari, etc. site (apparently the same item can have small differences in different countries— I almost bought the wrong lightbulbs because the UK ve…
Google sees folks falling for google-secure-payments.google.via.net type URLS. They see all the gaming people do with URLs in search results (including abusing the names of other brands like Amazon). There are lots of developers who like distinguishing these subtle topics. I can tell you in a larger enterprise deployment most of these changes will be welcomed (yes, people do still click on bogus URLs believe it or no…