Windows 7 Chrome dumps http://

[whoosh]

Link Removed - Invalid URL

Google has taken an interesting move in the latest developer builds of its Chrome browser. The company has stripped out the http://prefix from web addresses, leaving them to start solely with "www."
On the vast majority of sites, you'll no longer see those letters. Sites that use ftp:// or https://, however, will still display them - to keep support for these protocols. Also, if you copy/paste an address, the http://will automatically be added back in for the benefit of those not using browsers that support http://-free addresses.
Thom Holweda at OS News, who spotted the move, criticised Google for "hiding complexity" however, saying: " You can cover up that pile of mangled corpses in your bedroom with a flower-patterned table cloth, but that doesn't actually address the problem of there being a pile of mangled corpses in your bedroom".

 

[ChatGPT]

It appears you're bringing up a major change in user experience with Google Chrome that has sparked quite a bit of discussion. Let's break down this topic to provide a comprehensive overview. ## Overview of the Change Google's recent decision to remove the "http://" prefix from web addresses in the Chrome browser aligns with the trend towards simplicity in user interfaces. The rationale behind this shift seems to revolve around making the web experience cleaner and less intimidating for users who might not be as tech-savvy. ### Key Points:

1. Default Behavior:
   • Most web addresses will now appear starting with "www" rather than "http://." This is expected to streamline how URLs are displayed, possibly making them look cleaner and more user-friendly.
   []Protocol Support:
   • The change will not affect web addresses that utilize "ftp://" and "https://," preserving necessary functionality for these protocols. This means that while the visual aspect changes, the technical underpinnings remain intact.
   []Address Manipulation:
   • If users copy and paste an address, Chrome will automatically reintroduce "http://" for compatibility reasons. This ensures that users can still engage with websites even if they are less familiar with typing in full URLs. ## Criticism and Considerations Thom Holweda’s analogy about hiding complexity points towards an ongoing debate in web design. While removing technical jargon can make the web more accessible, it also raises concerns about users not fully understanding which protocols they are engaging with. This could potentially lead to security implications, as many users might not realize they are on an unsecured HTTP site versus a secure HTTPS one. ### Potential Implications: | Aspect | Implication |

     User Experience	Cleaner, less intimidating interfaces.
     User Awareness	Potentially reduces understanding of web security protocols.
     Website Adaptation	Sites may need to educate users on secure vs. non-secure protocols.

     ## Conclusion In an era where the web is continuously evolving, such design decisions can shape how users perceive and interact with web services. Balancing simplification with a robust understanding of web protocols will be key to ensuring user safety and satisfaction. If you have further questions or thoughts about this change in Chrome, feel free to share!