News for hackers. Stuff that matters.
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by nerdbaggy on Thursday April 25, 2019 @08:15AM (#19747231)
I wonder if this will ever evolve in emoji in URLs. I watched a short video about a guy who is squatting on most of the emoji domains
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by mojo74 on Thursday April 25, 2019 @08:55AM (#19747539)
I now have the image of a man squatting over the pile of poo emoji. I accept I will never grow up.
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by brndr on Thursday April 25, 2019 @09:37AM (#19747905)
I guess this site is relevant here: https://xn--ls8h.la/ (<pile of poop emoji>.la)

But apparently most TLDs don't support emoji URLs yet.

Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by Technetium_Hat on Thursday April 25, 2019 @10:54AM (#19748783)
the biggest barrier, in my opinion, is the ugly punycode links. most browsers still do not render them properly, and if they did, it would have false positives. (i.e. there is no way to tell if a string is intended to be punycode or not)
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by 0x0 on Thursday April 25, 2019 @11:11AM (#19748981)
It's not as much a matter of "still not rendering them properly", but more that they are doing it on purpose to avoid homoglyph attacks. Earlier browsers more OFTEN used to render them "properly", I believe.
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by SiempreViernes on Thursday April 25, 2019 @11:43AM (#19749314)
Of course, this only helps against foreign letters, you still have people squatting or putting phishing on common typos of pure asci urls with basically the same result.

Meanwhile, almost all of humanity still can't get decent urls in their native language :(

Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by bzbarsky on Thursday April 25, 2019 @03:58PM (#19751927)
> Meanwhile, almost all of humanity still can't get decent urls in their native language :(

Why not?

For example, http://xn--h1alffa9f.xn--p1ai/ renders the URL in Russian for me in the URL bar in all of Chrome, Firefox, and Safari (though Chrome converts to punycode if I copy the URL from the URL bar, unfortunately). [Edit: Also, it looks like HN's linkifier converts to punycode; what I wrote there is "россия.рф" and that's what HN has stored if I edit this comment.]

In more detail, for Firefox (where I can find this sort of thing quickly in the code), there are the following things affecting the display:

1) The "network.IDN_show_punycode" preference. This defaults to false, so punycode is not forced across the board.

2) There is a bunch of preferences for what toplevel domains are "safe" for use with non-ASCII chars by default no matter what. That option currently defaults to "false" as far as I can tell.

3) URLs the fit in the Highly Restrictive profile defined at https://www.unicode.org/reports/tr39/#Restriction_Level_Dete... are shown as non-punycode as far as I can tell.

4) There's some heuristic detection for URLs using multiple scripts at once and blocking that.

There are also preferences to force-allow or force-deny use of IDN with certain characters; those sets are empty by default.

In any case, the default behavior looks to me like a single-script URL in any language would be shown in IDN. Do you have a counter-example?

https://searchfox.org/mozilla-central/rev/75294521381b331f82... has the relevant preferences with their default values as of today.

Disclaimer: I work on Firefox, and have been involved peripherally in some of the IDN work.

Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by yuubi on Thursday April 25, 2019 @05:56PM (#19752870)
If it starts xn-- then it's punycode, and the prefix was apparently chosen because it didn't occur in any actual DNS labels.
Re:Chinese Number Websites: The Secret Meaning of URLs (2014) by billyhoffman on Thursday April 25, 2019 @11:42AM (#19749307)
This actually predates emoji (and was mentioned in the article). In the early 00's we got the ability to use unicode characters in a domain name. The example I always like was Unicode Snowman ;-)

http://xn--n3h.com/ (Funny enough HN is stripping the Unicode Snowman glyph, so using the puny code version)

Was a great way to break websites. JavaScript used for client-side validation usually allowed it, but backend code often didn't understand unicode for URLs, and would usually choke somewhere and (fingers crossed) give you a lovely J2EE or ASP.NET error page with some helpful stack traces and version numbers