Discussion Question for Web Devs and Server Admins.

Should we use unicode (Non-English/Latin) text in URL?

Eg: unicode blog title converted to use as permalink

I’d recommend you don’t.

Purely due to browser support, not everyone uses mainstream browsers, and URL parsing may become an issue if you’re using Unicode in your routes.

Also, a URL should generally be able to be typed in, as it informs the user where they are, generally better then navigation/breadcrumb menus.

Also, the only time I would expect Unicode / emojis in a URL, is when it’s purely a novelty.

http://👻💩.ws/

Or if that doesn’t work
http://xn--9q8h2c.ws/

@C0D4 ghostshit ?

@cursee I just picked 2 😂does it work?

@C0D4 on my chrome it auto redirect to the second.

@cursee that’s due to a Unicode security issue, so browsers redirect into the plaintext URL instead.

For example:
https://аpple.com

Used to bring you to this site
https://www.xn--80ak6aa92e.com/

@Brosyl good ol' beautiful https://xn--oi8h.com

@succcubbus @Brosyl @C0D4

So all emojis are prefixed with xn-- when transformed for url?

@cursee as far as I know, I haven’t dug deep into them.

Fun fact, using iOS, you can not click on the links with emojis, only the translated ones are clickable. But in the browser bar, you see the emojis.

@kimb damn iOS fully committed to emojis

@cursee @C0D4 any non ascii character is translated like this using Punycode

Please don't, next people will want it in their usernames and everything and it'll break databases everywhere 😰

Also I lost count of the times I went to emojipedia to copy-paste every time I wanted to type an emoji on desktop...