Chrome is now hiding "trivial" subdomains in the URL bar (www[.]domain[.]com shows only domain[.]com ). This is plain wrong, and buggy as hell :/ https://bugs.chromium.org/p/chromium/issues/detail?id=881410
@x0rz what the hell? What an antipattern
@x0rz my theory about this is that they will use it to hide the AMP subdomain and serve everything as amp by default
@aadilayub @x0rz
also just making people go through #Google when they want to search a site
a lot of users already search for stuff even when it's in their history, this change is reinforcing that behavior
@aadilayub @x0rz ding ding we have a winner
Embrace Extend and Extinguish
@rbe_expert @aadilayub @x0rz This game is too easy, I guess "EEE?" before rreading headlines involving Google and I haven't been wrong in years.
@x0rz
In nonenglish speaking countries it'll be like Google themselves handing user details to unknown parties.
@x0rz Oh, they're pulling a Microsoft now (with hiding extensions). That's ... definitely helpful. I always search around for how to disable that. Every. Single. Time. When I'm on a windows system ...
@x0rz I'm totally not seeing how this is ever going to be a problem *cough*
@x0rz Bloody hell.
@x0rz I think hiding m. is probably the worst offender, as now you're not sure whether this is how a site is supposed to look like, or whether it's the mobile version.
@x0rz it’s stupid is what it is and it’s the result of them pandering to the lowest common denominator. For some domains the www goes somewhere completely different to the domain. 😞
@x0rz that's crap ... didn't even notice so far :/ well, time to check if Google or Mozilla have solved the Gmail performance issues.
Thanks for the hint
@x0rz this is total BS. This will be about hiding their AMP crap so people don’t know if they’re getting that or the proper website - controlled by Google or not.
@x0rz As if the other things google does are right?
@x0rz saw this link in one of the comments: https://www.wired.com/story/google-wants-to-kill-the-url/
Even if people have a hard time handling URLs, how is it Google's responsibility to fix this? This sounds more like a usability rather than a security issue
@x0rz *cringe*