Care to Register Your Own TLD?

luap writes: "MSNBC is running this article about a Top Level Domain proposal by the Consumer Project for Technology to add the TLDs ".sucks," ".unions," ".consumers," ".complaints," ".ecology," ".isnotgreen," ".isnotfair," ".shareholder," ".taxpayer" and ".unite." Where are ".rules," ".isaloser," etc..?"

More TDLs are certainly overdue -- but ".isnotfair" and ".isnotgreen"? How about ".fam" for family? What new TDLs would make most sense? Would officializing ".sucks" do anything besides lead to companies buying additional domain names to sit on? These questions will do nothing but hover until ICANN acts on this or other TLD-loosening proposals, which so far it has been reluctant to do.

Comments

This is a joke, right?

[zpengo]

Some points to consider:

• The ".sucks" thing will never work. Every company that registers a ".com" will grab the ".sucks" as well, just in case. Microsoft will, without question, own "www.microsoft.sucks." The article says that companies will be prohibited from registering their own names under such a domain, but how can that be enforced? It goes against some very basic laws that give a company the right to control what happens to its name (a la eToys).
• TLDs are not mean to simply be clever endings to website names. They serve a purpose. If ".sucks" is accepted, then so must be every other clever idea that someone comes up with for a URL. Why not ".ate.my.balls," for example. Yeah, they're cute, and yeah, it would be nice in some ways to have more URL flexibility, but it goes against the basic purpose of TLDs.
• If it goes through, I have dibs on "www.linux.sucks" so that it can't fall into the wrong hands. *grin*

ICQ: 49636524
snowphoton@mindspring.com