Full list of new gTLDs
name.com
name.com
http://gtldresult.icann.org/application-result/applicationst...
We're heading towards a future in which TLDs are irrelevant.
This will give a good opportunity to the rest of us.
1) Much more complicated URL recognition regexp
2) Much more big Ablock Plus filter lists
3) ftnn2lhnosm.youtube
4) www.apple
I'm joking. I really don't like the new gTLD thing.
At least I'll be able to blacklist dQw4w9WgXcQ.youtube in my /etc/hosts and be able to blindly click links again.
Uh, if you try to copy it, Chrome prepends the http://. It's only a visual effect, it still pastes full links.
I don't mean to endorse GTLDs, of course; it's apparent that they're solely a caustic money-making scheme and have no fathomable benefits.
That rubs me the wrong way, and I'd rather not give my money to a company that thinks "hackers" are all criminals.
Edit: I got as far as checkout with a domain containing "hacker" so it looks OK on that front.
I'd recommend.
The problem: If you use their name servers, they install a wildcard record for the domain pointing at a crummy adspam page. You can override the wildcard record with your own, but not disable it completely, which is completely unacceptable.
Their explicitly stated reason for fucking over their customers is "we make more money this way". Which would be fine, but there's actually no way they'd be making even pennies on my domain, and they are actively reducing its utility by a much larger amount.
But more importantly, I don't see how this can possibly be an unfair criticism. They are providing a uniquely crappy service, and have shown what I consider to be a flagrant disregard for their customers by degrading their service for no benefit at all to name.com. It's stupid, it's evil, and it's bad business. Why in the world would I trust or recommend them?
(Just to be clear: I'm not complaining that there's a wildcard DNS record by default. Parking domains by default seems to be how everyone in the business works. I'm complaining about the fact that the wildcard DNS record stays in effect even after you configure the comain, and can only be disabled by defining your own bogus wildcard record instead. Basically it turns every user of their service into an unintentional typosquatter.)
Then again, ICANN has nothing to lose by encouraging many applicants, they get an awful lot of money from the applications (about 357 million [1]). They may be non-profit, but they still need money to keep running.
[1] http://www.name.com/blog/general/news-2/2012/06/icann-reveals-the-new-gtlds/I believe the rules state that a registrar selling these domains (which VW would then be) must give equal access to everyone (or something along those lines).
On the other hand, the new TLD only means just another name to maintain, as I don't think anyone will actually remove the ".com" domain when they get their own TLD. One of them will be redirected to the other, and for 99% of the time the custom one will be redirected to the older.
So really in the end, a custom TLD is just /more/ money they need to shell out for protecting their name online.
http://newgtlds.icann.org/en/applicants/customer-service/faq...
that said, ICANN's process has not inspired confidence that these sorts of requirements will survive. that someone wouldn't sell you a name under a new gTLD (e.g. under .apple, .google, .volkswagen, etc) is one of the problems they are trying to get rid of. why people applied for .brand names when the guidelines and FAQ suggest they'll be forbidden tells me one thing: they expect the rulebook to be thrown out. in the end, it's a cheap gamble.
the whole process, beginning to now, has inflamed a lot of ICANN watchers, and while i'm normally understanding and supportive of ICANN i tend to agree. this is careening to a cluster f---.
so none are actually approved (and few likely to happen)
EDIT http://newgtlds.icann.org/en/announcements-and-media/announc...
>> [The objection period has been] extended .. to 13 March 2013.
I was incorrect
(It appears to be one very long string of text, and I don't believe that
word-wrap: break-word;
is on for the comments, meaning that long words force a scrollbar.)2. See 1
3. See 2