[UA-discuss] IDN Implementation Guidelines [RE: Re : And now about phishing...]

[Dusan Stojicevic]

Hi Andrew,

If I want to expand the character repertoire of identifiers to encompass all
the chars humans use, I will get - Unicode. :)  As a person who want
Internet on Unicode, not on ASCII, this is something you can expect from me.
:) Now seriously, I agree mostly with you, "bug" is not new (the guy just
invest few dollars to get some thousand dollars for telling to Google what
we knew for many years), but - if we start to address this problem just as
"ASCII brands confusion with other scripts (and most brands are written in
Latin script)", soon we will get back to ASCII Internet - which is just
starting with making IDNs second-class URLs, and ending with no interest
from users.
And I agree with you - we will have a lot of potential confusion (whatever
we do to solve this), and that's what we need to discuss - maybe I am wrong,
maybe we need to use languages not only scripts, not sure - but this way,
how developers and registries are addressing this issue, is leading to an
end of IDNs as something usable.
And agree with you that this group can do useful things, that's why I am
here :)

Cheers, 
Dusan



-----Original Message-----
From: ua-discuss-bounces at icann.org [mailto:ua-discuss-bounces at icann.org] On
Behalf Of Andrew Sullivan
Sent: Friday, April 21, 2017 8:48 PM
To: ua-discuss at icann.org
Subject: Re: [UA-discuss] IDN Implementation Guidelines [RE: Re : And now
about phishing...]

On Fri, Apr 21, 2017 at 07:11:00PM +0200, Dusan Stojicevic wrote:
> Besides paypal, apple, epic, there is as much brands as you want, which
can be made from just Cyrillic chars: Coca-cola, Pepsi, Opel, IBM...

See Asmus's notes, but there's a basic problem here: there is at bottom no
way to fix this generally.  If you want to expand the character repertoire
of identifiers to encompass all the characters humans use, it is going to
come with a considerable risk of potential confusion.  There is nothing
remotely new about this.  (The only really new thing here is someone
successfully whipping up anxiety over this supposed "bug", and even that is
just a rerun of previous similar
events.)



I think this group could do some useful things.  For instance, if we funded
open code for variant calculation and found some additional people who were
willing to learn about the details (this requires at least actually reading
the Unicode spec) to pour into the i18n issues, I think that would be a
contribution.

Best regards,

A

--
Andrew Sullivan
ajs at anvilwalrusden.com


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus