- Joined
- Mar 28, 2005
- Messages
- 5,992
- Reaction score
- 149
.web has a shot at becoming a solid second choice to .com, probably similar to .net in popularity. I'd join the landrush trying to get a few generics. but it wouldn't replace .com
Or better, register wide.web, then you could have http://www.world.wide.web, the World Wide Web World Wide Web.I wonder if someone could register www.web? Then you'd have http://www.www.web, the World Wide Web Web.
Frankly, I think most people are missing the point. The real momentum behind this was the Introduction of IDN TLDs and the general expansion of TLDs was largely a sop to xenophobes to allow this to happen. However, I believe ICANN too have largely missed the point, as it is not the TLD which the Chinese, Japanese and Russians are really having problems with. It is the second level, which has in any case been there for a while. Paste an IDN.com into a field of Chinese text and then do the same with a Chinese IDN.IDN. Not difficult to see which stands out the most. Dot com is an established global brand. It is bigger than Coca Cola every market in the World. Every keyboard has the Latin Characters to produce it.
The only really solid argument for producing IDN.IDN is the incongruity of Right to LeftLanguages with Left to Right extension like dot Com. Yes, the Arabs, Iranians, Pakistanis and Jews need it. Of course if the case had been put forward on this basis alone, it would not have happened for another 100 years as the system is still very much still US-centric even though things are slowly changing.
What ICANN should have focused on is forcing out access of browsers that won't support Unicode characters. When IE6 attempts to access the DNS it should be kicked backed. It should be kicked backed because its presence is stiffling innovation in much of Asia. It should, however, also be kicked back because it is a security nightmare that only still exists because of the monopolistic position which Microsoft has unfairly gained in the browser market, and the total distain it is has subsequently shown for its customers.
ICANN should enforce Browser Standardisation as a prequalification for access to the Internet. Software writers should be forced to meet mimimum requirements before their browsers are given access to the Internet's addressing system.
As for dot Web, probably no harm in it, provided it is not infringing the Intellectual Property rights of existing TLD owners, but not really going to rock anyone's World. What people haven't noticed is that the presumption of renewal on New TLDs also infers the same on the Existing TLDs. It would seem that never again will Verisign have to compete in a beauty contest for dot Net or be challenged over their entitlement to run the dot Com registry.
They are long gone and so is our money.
Dear Mr. Rubber Duck,
While I value your contributions to this forum, personally I feel you are borderline on having a breakdown. You cannot inject IDN into every conversation, this topic, as with many others has nothing to do with IDN. I have IDN's, I like IDN's but your position as the mouthpiece for all IDN issues is not healthy when you do this. It's healthy when you are on topic, in the right place, at the right time but not in every thread regardless of the topic. It simply does not fit here. I hope your listening and don't take this the wrong way or offensively. I hope you hear what I am saying.
lol for gods sake Rubber Duck forget IDN's at least in one thread , you start LIKE :thank you but i think IDN IDN IDN IDN IDN IDN
If you had actually read the policy adopted by the ICANN Board, that enables the introduction of New gTLDs, or even the statements from Dr Twomney which are very much watered down for an English Speaking audience, you would know this has everything to do with IDN.
Yep, that is just about what it says in the policy statement adopted by the ICANN board if you actually care to read it!
*the exceptional businesses of our esteemed moderators