This is a nitpick but it bothers me. I just upgraded to the recent beta v2.1.0.beta2 +6 and now all profile name fields revert to the OS’s emoji set for names with emoji in them. Meta has this behavior. I renamed myself as a test. If you are on an iphone you should see the apple default, for samsung, the samsung default (this for me) and for a chromebook, the emoji for google (also for me). I can see that the emoji set used here is twitter; same as my site.
AI-generated summary
Selected emoji set does not affect name field
A user purldator reported an issue with the emoji set in the name field after upgrading to Discourse beta version v2.1.0.beta2 +6. The user noticed that the name field now uses the OS’s default emoji set instead of the site’s selected emoji set.
codinghorror explained that this is the intended behavior, as usernames are Unicode, and Unicode emojis are not allowed in usernames as a site policy. However, purldator disputed this, claiming that the Twitter emoji set previously worked for the name field on Windows.
codinghorror clarified that Unicode in the full name field is allowed to support all human languages. purldator insisted that the Twitter emoji set worked before, and suggested disabling emojis in the name field as a solution.
a) that’s always the way it has worked in Discourse; usernames are unicode
b) unicode emoji are not allowed in usernames here as a site policy
Then why did it work before? Is this a new policy?
It has never worked before to my knowledge. Maybe you are thinking of post bodies or topic titles.
Unicode in the full name field is sacrosanct, because that has to apply to every human language on earth.
Nope. It’s worked before. I distinctly remember the Twitter emoji on windows for the name field.
Then disable emoji in the name field.