ICANN Officially Approves .jobs and .travel TLD's

EyeMyke writes "As reported on News.com, ICANN has approved the .jobs and .travel domains, and is pending decision on .asia, .mail, .tel, and .xxx. One has to ask 'Will these new domains actually prove useful, or is ICANN just avoiding the real issues confronting them in regards to regulating domain registration?'" We've covered both of these domains before, but it would seem they are even more-approved now, or at least the process is important enough to warrant an official announcement from ICANN.

Comments

.xxx is potentially bad news.

[\\]

I don't really understand the point of a .xxx tld. You can usually tell from a domain name if you should be loading the url or not, it isn't like everything will be forced to use .xxx once the new tld exists.. unless..

If the point of .xxx is to force adult web sites into using it, how long until adult sites are sued into the ground for using other tlds? What if I'm running a french or italian language site with occasional boobies on it on a .com tld, would some tool force me onto a .xxx? Or even a .uk site?

Blarg. .xxx is perhaps more stupid than the entire artificial tld scarcity bit.

Re:.xxx is potentially bad news.

[ImaLamer]

If the point of .xxx is to force adult web sites into using it, how long until adult sites are sued into the ground for using other tlds? What if I'm running a french or italian language site with occasional boobies on it on a .com tld, would some tool force me onto a .xxx? Or even a .uk site?

Maybe the first step is to just create the xxx domain.

What I'd do (if I was ICANN or whomever):

* Create the xxx tld and then take a select bunch of dictionary words and sell them to pr0n friendly bandwidth/hosting providers.
* Make them the official registratrs for "free.xxx", "anal.xxx" or whatever.
* This creates more imaginative and available pr0n namespace (pr0n is always going to be number one)
* Allow ISP's or OS vendors to block xxx domain
* Stop accepting pr0n sites for .com, .net, .org, (and .edu and .mil)
** Don't get into censorship, unspoken agreement.
* Allow pr0n marketing on other tld's...
** Direct community of pr0n content producers to use the xxx tld when the content is obscene
** Example: playboy.tv is a site about the channel, but it doesn't have nude content. When you want nude you click into xxx tld, unless your parents blocked it.
** Example (2): Playboy.com is a portal to all xxx tlds but contains magazine content; all images are hosted on a xxx tld.
* Only send form letters to .com owners when enough people vote for it or something...

I think we can solve the "censorship" problem a lot easier that way. Make it transparent to content producers who want to go wild and they will adopt it fast, and that is all it takes. Build the porn, they will come (no pun intended).

Some say this approach will cause it to become USENET 2010, but I say that depends on content producers. If they want to create pointy.boobies.bobs.image.xxx let them - but they will learn right away that won't work.