Admins can change the set at /admin/config/emoji/settings?filter=emoji_set
If there’s an existing open-source set you would like to see available in Discourse, please let us know.
We understand that changing emojis can be a very visible change, but we didn’t have any other way around it. We prefer to lay a good foundation for the future by only supporting fully open-source sets.
Or is it just so admins are aware of this change, and the deprecated options will vanish without any consequences?
You can entirely disable emojis from the admin settings, but it won’t convert common text smilies such as :) as emojis.
Unicode emojis won’t be converted as images.
The emoji selector will be absent from the composer, which is not a loss on mobiles since all mobile keyboards have an emoji shortcut, but I think most people don’t know how to write emojis on a computer.
Also, cross-linking this as it’s also related to a future emoji set change:
different platforms support new released emojis at different speed, so you could have user A on platform 1, creating a post using an emoji available on this platform, which will then be seen by user B on platform 2 which doesn’t support yet the latest emojis released few weeks ago => tofu box (in the world of fonts, “tofu” is a blank rectangular box that appears when a character cannot be displayed).
custom emojis. Discourse supports custom emojis which are not mapped to a character and are just images.
No, standard is the unicode base representation, they also call it “sample”. I would recommend you try twemoji maybe? Or maybe fluent ui, or noto. Probably all good choices for more character.
I will look at this in the next 24 hours, maybe theres something wrong here. The only one expected to be smaller is the openmoji set, due to some specific choice they made.