interesting UA issue discovered
We have been advocating for more lenience in allowing new TLDs in linkification.... seems like we just found an interesting issue that propped up... One of the tools (social media one) converted a domain we were posting in brackets: (http://ymi.asia) into a link for "ymi.asia)" included the close-bracket in the link... accidentally creating a dead link, we suspect they tried to update their previous script to allow anything after the dot until a space... should we look into any of our documents to flag this?.. Edmon
Ha :) Good point! Lars -----Ursprüngliche Nachricht----- Von: UA-discuss [mailto:ua-discuss-bounces@icann.org] Im Auftrag von Edmon Gesendet: Dienstag, 30. Januar 2018 08:12 An: 'Universal Acceptance' <ua-discuss@icann.org> Betreff: [UA-discuss] interesting UA issue discovered We have been advocating for more lenience in allowing new TLDs in linkification.... seems like we just found an interesting issue that propped up... One of the tools (social media one) converted a domain we were posting in brackets: (http://ymi.asia) into a link for "ymi.asia)" included the close-bracket in the link... accidentally creating a dead link, we suspect they tried to update their previous script to allow anything after the dot until a space... should we look into any of our documents to flag this?.. Edmon
On Tue, 30 Jan 2018 08:11:45 +0100, Edmon <edmon@registry.asia> wrote:
One of the tools (social media one) converted a domain we were posting in brackets: (http://ymi.asia) into a link for "ymi.asia)" included the close-bracket in the link... accidentally creating a dead link, we suspect they tried to update their previous script to allow anything after the dot until a space... should we look into any of our documents to flag this?..
This is a *really* common problem in linkification tools in general. Wherever we talk about linkification we should flag it. Ultimately the solution is heuristic, but the saving of 2-10 seconds each time someone does this probably adds up to many lifetimes each year... cheers -- Chaals is Charles McCathie Nevile find more at http://yandex.com
On Tue, Jan 30, 2018 at 12:00:00PM +0100, Chaals McCathie Nevile wrote:
This is a *really* common problem in linkification tools in general.
I continue to believe that the guidance should include warnings about how poorly linkification works. The scheme of the URI, the path portion, and the host portion (what we think of as the domain name) are each areas that cause trouble. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com
I have only anecdotes about how well or how poorly linkification works in the real world. I am looking for a contact in Microsoft Office who might have some telemetry on linkification within Word, Outlook, PowerPoint, etc. (My small portion of the real world.) -----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Andrew Sullivan Sent: Tuesday, January 30, 2018 8:09 AM To: ua-discuss@icann.org Subject: Re: [UA-discuss] interesting UA issue discovered On Tue, Jan 30, 2018 at 12:00:00PM +0100, Chaals McCathie Nevile wrote:
This is a *really* common problem in linkification tools in general.
I continue to believe that the guidance should include warnings about how poorly linkification works. The scheme of the URI, the path portion, and the host portion (what we think of as the domain name) are each areas that cause trouble. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com
On Tue, Jan 30, 2018 at 05:15:49PM +0000, Mark Svancarek wrote:
I have only anecdotes about how well or how poorly linkification works in the real world.
The problem is that there are always corner cases; and one of those is, of course, the scheme itself. It's literally impossible to know in the abstract, and linkification engines therefore are mostly just hardwired to http(s). This is literally the same problem we're trying to cope with in TLDs, only in a different part of the URI. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com
My mail service protects me by converting all links in incoming emails to "safelinks".. What was the original strings which was converted? (Irony alert: Try sending it in a form which won't be identified by EOP as a link...) -----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Edmon Sent: Monday, January 29, 2018 11:12 PM To: 'Universal Acceptance' <ua-discuss@icann.org> Subject: [UA-discuss] interesting UA issue discovered We have been advocating for more lenience in allowing new TLDs in linkification.... seems like we just found an interesting issue that propped up... One of the tools (social media one) converted a domain we were posting in brackets: (https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fymi.asia&dat...) into a link for "ymi.asia)" included the close-bracket in the link... accidentally creating a dead link, we suspect they tried to update their previous script to allow anything after the dot until a space... should we look into any of our documents to flag this?.. Edmon
participants (5)
-
Andrew Sullivan -
Chaals McCathie Nevile -
Edmon -
Lars Steffen -
Mark Svancarek