Consider a Mastodon/Fediverse handle, like @[email protected] . What kinds of restrictions are there on "username"? Can I assume any valid unicode could go in there?

Somebody linked me RFC 7565, which linked to RFC7564, and if that's the place to look this appears to be the list of disallowed characters in a Fediverse username, and I'm cracking up because it's *mostly* stuff you'd expect, except the very first category of banned characters, specially, is "pre-1700 Korean characters".

The fediverse is welcome to all. EXCEPT KOREAN TIME TRAVELERS. Did you just wake up from being frozen in ice during the Joseon dynasty? The IETF is targeting you PERSONALLY

@mcc Oh! Yeah. It's because they don't have a well-defined canonical composition order, unlike modern Jamo, which do.

A weird bit of trivia: there is no composition for hanzi/kanji/hanja/chữ Hán characters (what many call "Chinese characters"). You can't just build one in Unicode. If you could, they'd also be in this list, for the same reason that Old Hangul Jamo are disallowed (which were only added because scholars needed them).

@Elizafox @mcc I regret to inform you, https://en.wikipedia.org/wiki/Chinese_character_description_languages#Ideographic_Description_Sequences
though afaik no implementation actually renders these sequences composed
Chinese character description languages - Wikipedia

@rcombs @Elizafox I AM NOW VERY EXCITED ABOUT USING THESE COMBINERS ON EMOJI, EVEN IF NOBODY CAN RENDER IT
@mcc @rcombs Jamo are canonicalised to a glyph according to a formula. There’s no such thing for the Chinese character composition characters. Unfortunately.