<div dir="auto">I think emoji is fascinating and potentially interesting to watch, and am not suggesting that emoji, once a bit more settled and standardized by those respective groups, may drift into our orbit. <div dir="auto"><br></div><div dir="auto">Rather, I am suggesting that we not allow it to distract us while working the existing issues.</div><div dir="auto"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On May 31, 2017 09:51, "Mark Svancarek via UA-discuss" <<a href="mailto:ua-discuss@icann.org">ua-discuss@icann.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Your explanation makes sense to me.<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> [mailto:<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@<wbr>icann.org</a>] On Behalf Of Andre Schappo<br>
Sent: Wednesday, May 31, 2017 9:49 AM<br>
To: <a href="mailto:ua-discuss@icann.org">ua-discuss@icann.org</a><br>
Subject: Re: [UA-discuss] SAC095 - SSAC Advisory on the Use of Emoji in Domain<br>
<br>
<br>
> On 31 May 2017, at 16:59, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>> wrote:<br>
><br>
> On Wed, May 31, 2017 at 03:49:21PM +0000, Andre Schappo wrote:<br>
>> My standard practice is to make, whenever possible, my links WYSIWYG. I think it a good practice. Sometimes it is not possible because of overly long and complex URLs.<br>
>><br>
><br>
> It's never actually been a recommendation from hypertext people,<br>
> however. They've always suggested that you should put links liberally<br>
> in running text that is in itself nicely readable. So,<br>
><br>
> <a href="target">In a previous post</a>, we discussed UA…<br>
><br>
> as opposed to<br>
><br>
> In a previous post, which you can find at <a<br>
> href="target">target</a>, we discussed UA …<br>
><br>
> Why do you think it's a good practice? It makes for very stilted<br>
> text.<br>
><br>
> A<br>
><br>
<br>
User reassurance - knowing the exact address of the website they will visit if they click the link.<br>
Transparency - stating clearly and exactly the address of the website they will visit if they click the link.<br>
User feedback - Users can visually verify that the address of the website they land on after clicking the link is indeed what was stated.<br>
<br>
I consider it makes for better security because the address is upfront for visual inspection/examination and not hidden behind some text string/image.<br>
<br>
There is much discussion/arguments on IDNs and phishing/spoofing because of, for instance, confusables.<br>
<br>
I consider spoofing/phishing is more easily achieved with links hiding behind text/images without going to the effort of employing and registering IDNs containing confusables.<br>
<br>
eg <a href="<a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FWeWillStealYourMoney.com&data=02%7C01%7Cmarksv%40microsoft.com%7C579786462f804689d6ed08d4a845192e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636318462118900393&sdata=I3WPZk7CBmK5Jldlr4VCaqySuyk80nHfjEidaFOYajw%3D&reserved=0" rel="noreferrer" target="_blank">https://na01.safelinks.<wbr>protection.outlook.com/?url=<wbr>http%3A%2F%<wbr>2FWeWillStealYourMoney.com&<wbr>data=02%7C01%7Cmarksv%<wbr>40microsoft.com%<wbr>7C579786462f804689d6ed08d4a845<wbr>192e%<wbr>7C72f988bf86f141af91ab2d7cd011<wbr>db47%7C1%7C0%<wbr>7C636318462118900393&sdata=<wbr>I3WPZk7CBmK5Jldlr4VCaqySuyk80n<wbr>HfjEidaFOYajw%3D&reserved=0</a>"><wbr>the honest and genuine bank<a><br>
<br>
I too used to hide links behind text/images but for about 4/5 years now I have been making links explicit as I consider it better security and better practice. One way in which I retain reading flow is to treat the link as a full stop ie terminating a sentence. Also, one can use links in a similar manner to the way citations are used in academic papers<br>
<br>
André Schappo<br>
<br>
<br>
</blockquote></div></div>