4 ms·
Well for one thing, web browsers aren't the only place domain names appear. Network administrators are people, too. Suppose you had to administer a server; th
by makecheck 17y ago
Well for one thing, web browsers aren't the only place domain names appear.
Network administrators are people, too. Suppose you had to administer a server; the task would be almost impossible without domain name patterns.
Take a proxy server, for instance. Right now, I can set it up by saying that domains "*.xyz.com" are local to my network, forcing everything else to go through the proxy. If every location were an incomprehensible name (as you suggest), the only way to configure the server would be to list every obfuscated name. It also wouldn't be future-proof; without a pattern, the server couldn't possibly determine how to handle a new machine name, so someone would have to go in and add more obfuscated names to the list.
- justin_vanw 17y agoI see what you are saying. why can't you say *.alsfjosajlksajdf, just the same as now? It's harder to remember, but encryption keys are literally impossible to remember and people maintain lists of those. So to be clear, the idea is just to take away any choice when you buy a domain name. Since people don't use domain names much to navigate around, and tend to use google, this won't change much. The domain is hidden and ugly, but otherwise works as per usual, perhaps I should have been explicit about that. Something else I should have been more explicit about: The whole point is to make it impossible to have squatting and lawsuits about domain names. Let a search engine decide what is the best 'flower' site, not who happened to buy flower.com in 1994. The current system inherently favors existing sites over new sites, which is silly.