Live data from Hacker News

Chrome hides www and https:// in the address bar again

bleepingcomputer.com

101–110 of 194 posts

Re: Chrome hides www and https:// in the address bar again

#101
post #74
post #55

I would have no trouble with hiding " https://" in the address bar, as long they show it for other protocols (including http). It might help move us to a world with https everywhere even faster. I still prefer Firefox: protocol, subdomains and path are greyed out but still clearly legible. This way I can eyeball "on which site am I?" quickly (and read google-secure-payments.google.via.net as via.net for example) and…

It seems that Firefox stopped copying http:// (when I want to copy URL) which is very annoying to me. I need the whole address when copying.

I have the opposite complaint: when I highlight a portion of the url in chrome, it prepends the http:// anyway. If I have the whole thing selected it would make sense to prepend the http://

Re: Chrome hides www and https:// in the address bar again

#102

This is a giant AMP scam. The next change will be that it will trick users into thinking they are on are on a real site like example.com but will instead be on Google.com/example.com. But chrome will remove google.com just like http/s.

Chrome on Android already hides the "google.com/amp" URL prefix for AMP URLs: https://blog.amp.dev/2018/01/09/improving-urls-for-amp-pages...

Re: Chrome hides www and https:// in the address bar again

#103
post #89

Earlier quoted context omitted.

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…

> Folks claiming google is hiding the owner of the website forget that the actual owner of the website is reflected by the END of the domain name, not the earlier parts. Perhaps this distinction could be made more clear by switching to reverse domain name notation.

There are lots of security manuals for beginners suggesting to look at the ends of URLs. Imagine the amount of confusion it will introduce.

Re: Chrome hides www and https:// in the address bar again

#104
post #81
post #45

Earlier quoted context omitted.

Finder on macOS does this too. It's maddening... There was an article recently about "hostile architecture" and this is similarly a "hostile software design" to prevent users from doing something the developers don't want them to do.

Its hostile for power users but it prevents grandpa from renaming 'IMG_144.jpg' to 'Idaho_grandkids', hammering enter on the 'are you sure you want this' nag screen and then wondering what broke his picture.

Does Mac still have resource forks? Either way, I'm sure it still has decent magic number decoding. Who (except family members in windows?) would care about the missing extensions?

The only real reason i care is for vim file detection (in Linux). How sad is that? :'(

Re: Chrome hides www and https:// in the address bar again

#105
post #81
post #45

Earlier quoted context omitted.

Finder on macOS does this too. It's maddening... There was an article recently about "hostile architecture" and this is similarly a "hostile software design" to prevent users from doing something the developers don't want them to do.

Its hostile for power users but it prevents grandpa from renaming 'IMG_144.jpg' to 'Idaho_grandkids', hammering enter on the 'are you sure you want this' nag screen and then wondering what broke his picture.

This was never a problem with classic Mac OS.

Files had a type code and a creator code. The type code told application whether they could open the file. The creator code told the Finder which application to open when the file was double-clicked.

It was impossible for the user to change either (in the stock OS).

Re: Chrome hides www and https:// in the address bar again

#107

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…

Why don't they display such URLs as:

via.net -> google -> secure-payments / whatever/whatever.html

I mean, I'd hate it, but at least it puts the public suffix up front and centre^Wleft. And it doesn't hide and part of the URL from the user, it just mangles it (but in a way that arguably enhances the user's ability to understand WTF they're looking at).

Re: Chrome hides www and https:// in the address bar again

#108
post #81
post #45

Earlier quoted context omitted.

Finder on macOS does this too. It's maddening... There was an article recently about "hostile architecture" and this is similarly a "hostile software design" to prevent users from doing something the developers don't want them to do.

Its hostile for power users but it prevents grandpa from renaming 'IMG_144.jpg' to 'Idaho_grandkids', hammering enter on the 'are you sure you want this' nag screen and then wondering what broke his picture.

On Macs before 2001, that used to work! We didn't used to cram pieces of file metadata into file names. File type was stored its own slot. The hidden-ness of a file was stored in its own slot.

I find it amazing that despite the industry's trend in recent years away from string-typing and towards static-typing, metadata-in-file-name just won't die.

I'm all for removing old ways of doing things that were bad, when we have a better way to do them. What we have here, with type-in-extension (and visibility-in-prefix), is a legacy system for which there is so far no workable substitute (on any system, much less all systems). A person can't be fully computer literate and not know what extensions are.

UTI has some nice features, but it's still based on extensions (which are keys into the database with the information you really want). This weird halfway point, where every user has to be a "power user" of the filesystem in order to not break their own files, will live on until either types are made primary again, or until we're all reduced to using standalone "apps" with app-specific storage and we can't share any data except as the app author decided to allow.

Re: Chrome hides www and https:// in the address bar again

#109

This is great and all until you (like me) need to be able to differentiate www.example.com from example.com and https:// example.com versus http:// example.com. My website doesn't forward example.com to www.example.com (due to errors on my part that I don't know how to fix, my email is in my profile and if you can help I'd greatly appreciate it). I don't know if there are any scenarios in which a properly-configured…

HTTP headers are hidden. That's great and all until you need to examine them for some development task.

iframe URLs are hidden. That's great and all until you need to verify that your iframe is loading the correct content.

Yet people don't complain about these. They are happy using the dev tools to access this information that is sometimes useful for developers and almost entirely useless for ordinary users.

Re: Chrome hides www and https:// in the address bar again

#110
post #42

This behavior will train users to believe that the www in domains isn't important, when it actually serves a very important purpose. You can't cname example.org, which makes it very hard to use a CDN to serve it unless the CDN provides anycast ips or you delegate DNS to the CDN. If they're intent on making the address bar useless, they may as well go full hog, like Apple does in desktop Safari -- the address bar show…

The "www" isn't important for the huge majority of users the huge majority of the time.
Post reply on HN