31–40 of 118 posts
Earlier quoted context omitted.
It's not white, it's the blueish grey #E1E8ED. You need a better monitor :)
Very much depends on what browser/platform you're on. Many different emoji implementations out there.
This is using Punycode encoding, see https://en.m.wikipedia.org/wiki/Emoji_domain .
Why is this even a thing?
So Punycode wasn't specifically designed to work with emoji, it just happens to work with emoji because emoji are part of Unicode.
And how do i type that in the address bar?
Earlier quoted context omitted.
Why is this even a thing?
Imagine if DNS consisted only of Arabic characters. Imagine how grumpy you'd be that you couldn't go to newyork.gov.us for your local government website, and instead had to go to نيويورك instead? Assuming you can't read Arabic, how on earth would you even recognise that address, let alone remember how to type it.
I always assumed the non-latin-alphabet people know their way around this because they already used the internet before unicode-domains.
There already is an emoji for apple (the fruit, not the company). Oh the horrors. I should start an emoji NIC!
Earlier quoted context omitted.
Very much depends on what browser/platform you're on. Many different emoji implementations out there.
Nope, Twitter replaces the unicode character with an SVG image, so it should show the same for everyone.
Earlier quoted context omitted.
Nope, Twitter replaces the unicode character with an SVG image, so it should show the same for everyone.
Depends on how you're browsing. The legacy fallback does not replace it, eg when you have js disabled
Earlier quoted context omitted.
if you run pihole or a local dnsmasq/unbound it should be possible to mitigate it by sinkholing any unicode domains, e.g. with dnsmasq (requires a patch https://github.com/spacedingo/dnsmasq-regexp_2.76 ) you can do this: address=/:xn--*:/0.0.0.0 does anyone know if something like this is possible with unbound?
But... What about legit unicode domains? I own a couple that I use for personal projects or file sharing.
Earlier quoted context omitted.
Imagine if DNS consisted only of Arabic characters. Imagine how grumpy you'd be that you couldn't go to newyork.gov.us for your local government website, and instead had to go to نيويورك instead? Assuming you can't read Arabic, how on earth would you even recognise that address, let alone remember how to type it.
Well, I'd probably had to learn something like this: https://en.wikipedia.org/wiki/Arabic_chat_alphabet I always assumed the non-latin-alphabet people know their way around this because they already used the internet before unicode-domains.
I hate to be a spoilsport, but this is a good reminder that https://en.wikipedia.org/wiki/IDN_homograph_attack is still possible in some domains and with some browsers and CLI tools, although some of the easier tricks to detect have been mitigated.
if you run pihole or a local dnsmasq/unbound it should be possible to mitigate it by sinkholing any unicode domains, e.g. with dnsmasq (requires a patch https://github.com/spacedingo/dnsmasq-regexp_2.76 ) you can do this: address=/:xn--*:/0.0.0.0 does anyone know if something like this is possible with unbound?