3 ms·
This is why Chrome should be viewed with skepticism. It's great for people who know how to use the internet, but what about those who don't? Type something ri
by because 14y ago
This is why Chrome should be viewed with skepticism. It's great for people who know how to use the internet, but what about those who don't? Type something ridiculous in the Address Bar (Google is trying to rename it the "everything bar" or whatever silly name they've come up with). Put a dot where it does do not belong. Mistype or mispell something. Runwordstogetherinalongstring. What happens? You get a Google controlled result. This is not insignificant. (Sorry for the double negative.)
As a knowledgeable programmer, your internet experience with DNS and browsers is very different from others, because you know what you're doing. Many people do not.
Should we teach them? Or should we try to control them by controlling "default behavior"?
Many people reading HN are probably too young to remember the browser wars and the battle over the "default browser" setting. This is why IE triumphed over Mozilla. And as any web developer knows, the web has suffered for it. Users who knew what they were doing could change the default settings. But that did not make the difference. Chrome is highly configurable. But that will not make the difference. Default settings are what matter the most.
The success of ICANN relies on a default setting. It's called "root.hints" or something similar. If a person running a DNS server (that could be anyone, including the end user) changes this setting, they can bypass ICANN and these landgrab gtlds.
In the distant past, "alternate roots", an early reaction ICANN's abuse of power, failed because they were trying to do what ICANN is now doing: make money by selling registrations in additional, redundant gtlds. Perhaps the "alternate roots" of the future will be noncommercial ones that subtract gtld's, not add them. For example, maybe we as smart users will choose to use a "pre-landgrab" root that does not have all these silly redundant gltd's that try to capture whatever unorthodox string a novice user might type in a browser.
Domain names are important, but always remember that those who seek to control the browser can easily subvert DNS. Given this decision from ICANN to sell out (which others, not just Google and Amazon, are following: e.g., the founder of BlackHat is running the newgtld program for ICANN; the author of BIND is partnering with a domainer to run a registry), we're going to see some aggressive moves from commercial authors of browsers to control type-in navigation. Of that you can be sure.
Again, the question is whether we want to teach users how things work, or whether we want to let them remain ignorant so we can control them. In the big picture, ignorance does not help the web. Though it may benefit certain vendors.
- icebraining 14y agoOr should we try to control them by controlling "default behavior"? Who's "we"? I'm not a browser programmer and I have no ability to do that. Frankly, I dislike this common idea that we all part of this common team just because we happen to know something more about computers than the average schmoe. I certainly don't have the power to control any important defaults and therefore people, do you? And while I can understand the goal, frankly I'm rather skeptical of our ability to teach most people, or of their willingness to be taught, which comes to much about the same. And I'm not sure if they're wrong in not wanting to waste valuable hours of life learning about a bunch of technical stuff that they don't really have much control over. If a person running a DNS server (that could be anyone, including the end user) changes this setting, they can bypass ICANN and these landgrab gtlds. But why should we do that? Why do you care? So some companies get shorter domains, so what? We don't even know if those generic TLDs will be accepted. Much ado about nothing, really.