Marcos, At 2016-04-22 15:27:42 +0200 Marcos Sanz <sanz@denic.de> wrote:
Note that both Firefox and Chromium refuse to display the hieroglyphics in the URL bar. My guess is that they display any IDN that they don't understand as punycode in order to minimize semantic attacks (I think there is a hieroglyph for the sun that looks like a circle that I guess could be confused for zero, so maybe this makes sense? maybe?).
since I had to do with this in the past, I happen to know how Firefox works: https://wiki.mozilla.org/IDN_Display_Algorithm
The summary -after recursive resolution of all nested document calls- is that hieroglyphs are candidate characters for exclusions from identifiers, according to the Unicode Consortium: http://www.unicode.org/reports/tr31/#Table_Candidate_Characters_for_Exclusio...
Hm... interesting. Since these are candidate characters, one could argue for any given character set to be included. I guess VeriSign should be doing that since they are the only TLD that claims to support this character set, but apparently they don't care that much.
But your animated gif got a smile in my face.
It's just a link, Pirate Bay style. "No copyrighted material hosted here, blah blah blah..." ;) BTW, I had a look at the server logs and there were 45 unique IP, 24 from IPv6 hosts. Well done, RIPE DNS working group! Cheers, -- Shane