Hacker News new | ask | show | jobs
by rehashed 4843 days ago
What benefit do these new TLDs bring to the table? If ICANN need additional revenue, why not fractionally increase the cost of the current gTLDs instead of introducing more?

All these new domains can possibly achieve, IMHO, is to confuse the consumer and allow corporations to control access to 'desirable' gTLDs.

If the domain space is so overcrowded, then by all means introduce a new gTLD - but keep it ICANN controlled. Either run a poll to choose, or allow the corporations to 'sponsor' their choice of TLDs incorporation into ICANN - but there is no way they should be commercially controlled!

UPDATE: Im really upset that I missed this - looks like ICANN opened up a discussion for public comment (which has now closed after only a month? Surely such a major change should be open to larger public debate..): http://www.icann.org/en/news/public-comment/closed-generic-0...

UPDATE2: I have sent an email to karen.lentz@icann.org requesting that the discussion be reopened. I believe it is our duty as a community to publicise this discussion amongst web professionals and have a further chance to fight it. I would respectfully request that you do the same!

1 comments

UPDATE3: The more I think about this, the more concerned I become. These new gTLDs, given the proliferation of combined search and location bars in modern browsers are tantamount to a direct keyword to those corporations with $185k to spend. Type in 'antivirus', and you will be directed to symantec - not the search results you would likely expect. This has to stop - NOW.
Searching from the URL bar has always been a bad idea, too bad Google adopted the practice.
That's hardly a reason to stop the new TLDs, you just need a rule that says you can't have A/AAAA records on the new TLDs.
There are many reasons. That is just one of them.

Please see parent and other posts in the thread, comments on the linked article, and discussions in the forums for others.

you already dont/wont have naked tld records because of local addressing: http://www/ becomes http://www.mydomain.com/ inside my os as directed by my dhcp server.