[Rubber Duck]

Originally Posted by drbiohealth

Well, this can only be significant if the masses use it, which appears not the case. Even I became aware of this short-hand technique after reading some post on this forum. If people prefer typing the complete URL in the address bar, the complexity of .extension of IDN will become important in deciding which .extension will ultimately be preferred. Normal logic: river water always follows the path of least resistance. Another secondary factor here is, which .extension would move faster and feed the masses first. Moreover, it needs to be seen how the end-user (industry) laps this opportunity.

I am curious to know if IDN.IDN .ccTLDs exist in chinese/japanese as of now? If they do, then ICANN needs to buck up before people there start getting addicted to IDN .ccTLDs.

I see that if there are no IDN.IDN ccTLDs for languages like Russian, Arabic, Indic for next two years or so, IDN.IDN in .com will have a chance there.

Only Chinese and I believe Korean as well, but yes they do resolve. ICANN definitely needs to get it finger out of its arse, or it won't have one to sit on at all!