Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

bleepingcomputer.com

Post reply on HN
Print view View original

141–150 of 194 posts

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

#141

Post by cm2187 »

astrobe_ wrote: post #95
jorvi wrote: post #81

Earlier quoted context omitted.

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.

It's not the picture that broke, it's not the user that is dumb, but the system that is broken. Dot extensions is a concept that should never have seen the light of the 21st century. Or at least it should be a last resort for the system to guess the file format for those formats that don't have magic numbers in their headers or for lesser known formats.

Or more generally the header should contain the metadata of the file: date modified, filetype, comments, icon, etc, rather than spreading that between the filesystem (with different filesystems having inconsistent dates), the OS, etc.

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

#142

Post by im3w1l »

jorvi wrote: post #81
mholt wrote: 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.

I like the design principle "it should be easy to do easy things and possible to do hard things". Showing the extension, but requiring terminal use to change it would a decent compromise.

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

#143

Post by ksherlock »

dreamcompiler wrote: post #125
e12e wrote: post #104

Earlier quoted context omitted.

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? :'(

Resource forks are still supported. At least they were with HFS+. They might be gone in APFS. In any case with each release Apple makes it harder to access them.

APFS still supports resource forks. (They're not as baked-in as HFS/HFS+, though.)

APFS has good extended attribute support. Whereas linux extended attributes might be limited to 64k, APFS extended attributes can be significantly bigger (I just created a 32MB one).

The xnu kernel has some ugly hacks (pre-dating APFS) which make the "com.apple.ResourceFork" available as a file ("/..namedfork/rsrc").

On HFS/HFS+, file/..namedfork/rsrc will always exist (and usually be empty). on APFS, file/..namedfork/rsrc will generate an ENOENT error if the resource fork/attribute doesn't exist.

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

#144

Post by mrkstu »

thaumasiotes wrote: post #135
yrro wrote: post #105

Earlier quoted context omitted.

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).

> It was impossible for the user to change either (in the stock OS). That's... much, much worse than dot extensions.

He's mis-stating it slightly. You couldn't fiddle with a file's creator code, but there wasn't much reason to.

The type codes were editable, in the sense you could choose the default app you wanted to open files of that type, which is really what you'd want to modify most of the time.

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

#145

Post by mrkstu »

twodayslate wrote: post #69
Consultant32452 wrote: post #59

Earlier quoted context omitted.

And requires you to jump through non-obvious hoops to make "hidden" files and folders visible.

Command + Shift + Period to show hidden files. To show extensions you can enable the setting in Finder's preferences under Advanced.

Nice, didn't know that one- very handy.

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

#146

Post by tyingq »

Rebelgecko wrote: post #5

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…

Urls are a blocker for AOL^h^h^h Google keyword plans.

Joking, but surely it's in Google's interest for the omnibar to just be a keyword search tool. Plebes don't need to know about urls.

Curious what Apple's position is.

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

#147

Post by csours »

dwild wrote: post #120
csours wrote: post #101

Earlier quoted context omitted.

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://

I can't reproduce what you say, it doesn't prepends http:// in my case. Are you on Windows?

Yes, on Windows. You do have to select the first part of the url, but I often just want the host and port, ie localhost:8080 instead of http://localhost:8080

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

#148

Post by annadane »

dlandis wrote: post #24

It's just so bizarre how strongly the Google product people continue to insist that this change is beneficial to users when so many users themselves simultaneously insist that it's not. Combined with the fact that their explanation is dubious at best (i.e. www is not a technically a "special case"), I find it very hard to believe they do not have additional, confidential reasoning for making this change.

Yeah forums where the company "interacts" with users is great.

"This change is beneficial." "No, it isn't." "Yes, it is." "But it isn't!" "We respect your feedback but we're implementing it anyway."

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

#149

Post by toast0 »

fadisaleh wrote: post #40

Can someone help me understand why this is a big deal? Safari has had this change for a while and I haven't felt like I'm missing anything. Where's the slippery slope? Does have to do with AMP?

Here's a problem: people often share screenshots with the address bar in the screenshot.

If they share it from Safari with default options, the address is mostly useless, it's just the domain (and www may elided), but it doesn't even look like a url, so whatever.

If they share it from Chrome with these new options, if it's like the last time Chrome released this, it looks like the full url, but it's not:

When you go to https://example.org/some/deep/url it may very well not be the same as https://www.example.org/some/deep/url and adds an extra layer of confusion to figuring out whatever the issue is.

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

#150

Post by jedimastert »

_8j50 wrote: post #6

URLs represent and identify content,controling them means you control content. In the short term these changes mean little but in the long term this will benefit google immensely. Google just loves slippery slopes. Identity and payment are extremely important to any ordered system of social interaction. More than content itself,controlling them helps one control everything else. I am trying hard to avoid believing co…

> Google just loves slippery slopes.

So, you fully admit to making a slippery slope argument?

Post reply on HN