What's the reason we're using libraries such as Twemoji here? All major OSs support emoji now and have their own set, meaning it would probably be easier to store the characters as such (using utf8mb4) and not worry about parsing them. That would not only allow compliance with the specifications but also mean that the emoji you type in the text field remains the same (for you) after submitting your post, instead of being replaced with some variant.

What's the reason we're using libraries such as Twemoji here? All major OSs support emoji now and have their own set, meaning it would probably be easier to store the characters as such (using utf8mb4) and not worry about parsing them. That would not only allow compliance with the specifications but also mean that the emoji you type in the text field remains the same (for you) after submitting your post, instead of being replaced with some variant.

Because emojis are not consistent across browsers and support for it is lacking in some browsers (ie. Emojis are all black/white in Mozilla Firefox), we use the Twitter Twemoji library (https://github.com/twitter/twemoji) to convert emoji characters to standardized images.

The emoji set differs between pretty much all operating systems be it iOS, OSX, Android, Windows, and Unix distros. Even between different versions of each of those systems the emoji set can be different.

The emoji set differs between pretty much all operating systems be it iOS, OSX, Android, Windows, and Unix distros. Even between different versions of each of those systems the emoji set can be different.

Them being different is no issue, it's when they're not supported that it becomes a problem.