Ask HN: Shouldn't gTLDs be non-generic?
Shouldn't the gTLDs express directly the company itself?
I can understand let's say '.apple', but '.app' is just too much. Yeah, Apple runs an "App Store". But, be serious they are not the only ones and that doesn't give you any rights over such a generic TLD. The same applies for mostly all other name grabs.
If they want their own TLD kingdom then let them be, but not by powering them with such generic ones. It is so clear that these companies don't have any intention to make these TLDs publicly available.
Can anyone clarify me how these things got through?
23 comments
[ 4.8 ms ] story [ 24.8 ms ] threadHow are those non-standard .cc addresses working out for everyone.
Plus greed on the part of ICANN. You can only sell one .google TLD, but there are thousands of relevant words in the dictionary for anyone with a deep enough coin purse.
UPDATE: Aha, "to" has an A record. It doesn't respond to an HTTP request for me but it does exist at least.
UPDATE2: OK, there are quite a lot: http://ydal.de/a-records-on-top-level-domains/ .. http://dk/ goes to the .dk registry.
On the other hand, I'm sure they'll make them publicly available - for the right price.
I'm not sure how the gTLD are supposed to work technically, but it seems to me that VeriSign made a mistake when registering the Hebrew '.com': Their version uses the Holam diacritic (the dot over the middle letter), which is not used in every-day Hebrew (it's mostly used to teach reading and to differentiate between different words with the same spelling, when such a thing might cause confusion). In any case, most computer users in Israel don't even know how to add diacritic marks, so I don't see anyone typing such an address in their browser.
Were any alternative methods of allocating TLDs ever proposed?