Hi all.
I have mixed feelings about linkification but I believe that, if implemented, it should be done without second-guessing or restrictions to the form “*.TLD” - otherwise we take the risk of doing what SW programmer did in the past, and that is at the root of the current UA problems, i.e. making assumptions based on the existing formats forgetting that new formats might be introduced as long as they comply with protocols.
Let me give an example. If I can type in a browser g-20.in, or G-20.in, or G-20.In, or G-20.IN, or more variations and still get to the same web site it would be wrong to introduce differentiation in linkification when those do not exist for the browsers.
Moreover, the same considerations should apply to IDNs.
Cheers,
Roberto


On 07.12.2018, at 10:40, Andre Schappo <A.Schappo@lboro.ac.uk> wrote:


With Respect To the auto linkification:

It seems to me that auto linkifying only a correctly formed lower case ASCII domain name would solve cases such as the G-20 example, below.

Actually the same auto linkifying principle could be applied to Cyrillic domain names and possibly other scripts that have case.

André Schappo

On 6 Dec 2018, at 18:05, Elaine Pruis <elainepruis@gmail.com> wrote:

This thread on twitter is telling.

On Wed, Dec 5, 2018 at 1:32 PM Ram Mohan <rmohan@afilias.info> wrote:
To be clear, Twitter did it right.

On Wed, Dec 5, 2018, 7:19 PM Elaine Pruis <elainepruis@gmail.com> wrote:
I'm really hoping this doesn't make Twitter rethink their plan to expand the list of TLDs that get linkified!


On Wed, Dec 5, 2018 at 10:14 AM Asmus Freytag <asmusf@ix.netcom.com> wrote: