Submitted via IRC for TheMightyBuzzard
Google Chrome developers advised they would wait until Fall or Spring to disclose how they would "kill" URLs, but it appears the endeavor has already begun: users have found that the latest build, Chrome 69, hides the "WWW" and "M" subdomains in the address bar. Bleeping Computer has instructions on how to restore what Google insists is "trivial."
(Score: 2) by isostatic on Thursday September 13 2018, @07:14AM (4 children)
I switched back to firefox a couple of years ago as I was worried about how much power I was giving google (also moved to duckduckgo -- when they introduced their uk specific version)
I still keep chrome though because when I connect to a https site with a self signed cert - like an ilo - I can actually connect to it easily in chrome.
(Score: 0) by Anonymous Coward on Thursday September 13 2018, @11:42AM (1 child)
Chrome will block you. I for one hate our new data sucking overlord.
(Score: 2) by isostatic on Thursday September 13 2018, @10:05PM
Chrome allows you to do two clicks to get past.
Firefox requires you to open another dialog, view the certificate, then make an exception
(Score: 0) by Anonymous Coward on Thursday September 13 2018, @11:52PM (1 child)
Don't worry. Firefox will be hiding "www." and "m." before long.
(Score: 0) by Anonymous Coward on Saturday September 15 2018, @10:48AM
Why would they do that?