The following proposed additions are for compatibility with other messaging and mail systems.
- ZIPPER-MOUTH FACE
- MONEY-MOUTH FACE
- FACE WITH THERMOMETER
- NERD FACE
- THINKING FACE
- FACE WITH ROLLING EYES
- UPSIDE-DOWN FACE
- FACE WITH HEAD-BANDAGE
- ROBOT FACE
- HUGGING FACE
- SIGN OF THE HORNS
- CRAB
- SCORPION
- LION FACE
- BOW AND ARROW
- AMPHORA
Most Popularly Requested Emoji
- HOT DOG
- TACO
- BURRITO
- BOTTLE WITH POPPING CORK
- POPCORN
- TURKEY
- UNICORN FACE
- CHEESE WEDGE
I cannot find an image of what Unicode character 'SIGN OF THE HORNS' looks like, but I hope it's fucking metal.
I still think it's wrong that there is no 
, though.
What, still no BUTT emoji?!
(_*_)
I really hope people implement HUGGING FACE as a smiley with a facehugger attached to it.
I dug through their meeting minutes and found the source of the proposal, at least: PDF: "Emoji-System Compatibility Additions"
It's apparently to encode Gmail's "Rock On" image.
Here, I screenshotted the bit from the PDF for you:
Also, Unicode humor from the mailing list:
(U+1F4A9 is of course 💩
Your blog software eats emoji?
(U+1F4A9 is of course PILE OF POO)
The blog software (WordPress) relies on a database (MySQL) which until relatively recently didn't implement Unicode's hyperspace beyond the Basic Multilingual Plane. Between PHP and MySQL of course actual error-handling is out of the question, it just truncates the input. JWZ presumably doesn't think that it's a good idea to manually install a newer MySQL and try to fix the database schema. Which you could see as cowardice, or else just as good sense.
I looked into it and it seemed like more trouble than it was worth. Feel the pain: herp, derp. You have to alter tables, which means a full export and re-import and god knows what will break, plus, making that work at all requires MySQL 5.5.14 or later and my system still has 5.1.73. Upgrading MySQL is, in my experience, as dicey a proposition as upgrading glibc and breaks everything else running on the system, so I think I'll just live without emoji.
You can type them out in 💩 form: 💩.
I would not have waded that far into that shit heap, so kudos to you for testing your sanity in that way. I bet you could write a JavaScript module for WordPress to find Emoji in a comment and convert them to the HTML entity format, but I suspect we can just all live with the current situation.
The JavaScript idea would only work if the emoji were still present in some form by time the page gets to the browse, but I think either MySQL or WordPress strips them out while assembling the page, so there's no way for JS to know that they were ever there.
Or, to summarize: not everything can be fixed retroactively by JavaScript.
I meant "fix client-side before comment submission", which could almost certainly be made to work but is probably not worth the effort.
That is moderately metal.
Different associations, indeed.
HUMAN PRIORITIES: Year of our Lord 2014
HOT DOG
TACO
BURRITO
BOTTLE WITH POPPING CORK
POPCORN
TURKEY
UNICORN FACE
CHEESE WEDGE
I think the Zoso symbols should get in before Prince. Based simply on age. :-)
Email me what you know about the emoji Unicode mysql troubles. Should be doable, I think. Painful, maybe. But doable.
Cf. https://twitter.com/libraryofemoji