3 ms·
It's not that hard to come up with legitimate domains in non-Latin script that could be recognized as word written in Latin script. For example, керас is a Russ
by mynegation 10y ago
It's not that hard to come up with legitimate domains in non-Latin script that could be recognized as word written in Latin script. For example, керас is a Russian transliteration of Keras. So I imagine they would get a bit of false positives and (fair) claims that non-ASCII languages are oppressed. To me, better alternative would be to limit puny code names to punycode TLDs, and make sure that no two TLDs look the same: task of much smaller scale.
- hyperpape 10y agoIt's not necessarily a matter of oppressing non-ASCII languages if it's a symmetric relation. So if "epic.com" is registered using ASCII, that precludes registering the cyrillic version, but if it's already registered in cyrillic, that precludes it being registered in ASCII. There is a starting advantage for ASCII because so many domains were registered from English speaking countries in the early years of the web. But non-ASCII using countries are just as vulnerable to this attack.
- codedokode 10y agoMaybe non-latin domains should use non-latin TLDs? Or at least registrar should reserve all alternative spellings when registering a domain.
- mynegation 10y agoYes, that was my suggestion: non-Latin domains MUST be in the non-Latin TLDs, with additional constraint that non-Latin TLDs cannot look like already registered Latin TLDs. In a twist of irony, Russian word "сом" (roughly pronounced as "some") means "catfish" (the animal, not the action of catfishing though).