emojilib & GitHub

• 🇺🇾 uruguay
• 🇬🇧 gb
• 🇺🇸 us

iamcal/emoji-data & Slack

• 🇺🇾 flag-uy
• 🇬🇧 flag-gb
• 🇺🇸 flag-us

How to proceed?

I'm not currently sure where these short names/codes come from. Is there some sort of standard? Should I open a request with iamcal/emoji-data, or should I change emojilib to use the flag-* format?

Note: I am trying to get emoji-mart to work correctly. See missive/emoji-mart#96 for more info.

Hey, @muan - accepting PRs for this project? I have a CLI tool combining git commits and emojis (commemoji) that I'd love to get in your README. Let me know and I'll get you a PR ASAP. ⭐

First of all, thank you for maintaining this repository!

I wrote a rudimentary emoji search program using your data, and noticed that, for example, "poop" does not match any of the keywords for 💩:

Another example I ran into was for 📱:

Finally, and I write this sincerely, I'd like to discuss 🍆:

I suggest that a section be added to CONTRIBUTING.md or README.md that gives guidance to future contributors about questions like these.

…and that's how I posted a GitHub issue about poop, cell phones, and penises 🤪

Cool! It looks like Instagram is using emojilib.

Maybe worth adding it to the Powered by, or a separate Used by list?

#braggingrights

Background:

I just remembered that my reasons for removing the names from 3.0 was because the name as an obvious keyword is available in unicode-emoji-json already. Sorry for the troubles.

#195 (comment)

It seems to me that #199, #200, and #201 might all be caused by the same issue. One of the motivation for using the emoji character as the key instead of text name as the key was because the unreliable nature of their emoji names. The text names might change, and when we edit emojilib there isn't an easy way to keep track of the name is so we can't really effectively exclude it from the keywords, therefore we might as well try to be thorough.

😔

Even the much referenced WEBFX Emoji Cheatsheet doesn't list its source or mappings. Github does, but I want to find out which code system is the most popular/used one - or rather which one's exist. I want to build an application that allows anyone to use emojicode in any application and any os and would appreciate any pointers in the right direction as to where I can find more information about the various mappings that exist already.

It seems like your latest version has stripped some alises. For example "🙏" should match pray.

It looks like there were a bunch of emojis added since v2.2.9. Any chance we might see an official release soon?

Hey.

Thanks for this library. It has been very helpful.

Are there any plans to add support for Emoji 11?
https://emojipedia.org/unicode-11.0/

Twitter have already updated to support the new emojis, Microsoft have added support in the Windows 10 insider build and EmojiOne are planning on releasing in the first half of August.

I could give you a hand ✋

💰💰💰💰 In https://github.com/muan/emojilib#electric_plug-powered-by-emojilib.

cc @notwaldorf

Some of the emojis are missing, which are among people, building and fruits etc.

[Originally raised here: https://github.com/notwaldorf/emoji-translate/issues/22]

If I type honey, a bee comes up,
If I type bee, a honey pot comes up.

🤷‍♂️

👍 💼 though, it's 🇬🇧!

(I've just discovered typing "great" brings up the "Great Britain" flag 🥇 )

There are a lot of new emojis missing in the json file.
How you're updating the list? manually?
I thought about adding some, but there are too many to add 😮

By this emojis list (from unicode.org), there are around ~2600 emojis and in the file here the are around ~1400. It's not that practical to add them manually, that's why I'm asking.

Thanks!

Hello,

New emojis are missing, like yawning, pinching hand, white heart, and more
🥱🤍🤏🏻
Can you please update the list ?

A plugin I use seems to use your library so I updated it locally from now

you should add a hurt hand hurt leg with both boy and girls plus a fast recovery and more

Very much outdated readme.

Please consider including the GitHub autocomplete emoji names in the library (full list here - https://api.github.com/emojis) as the names in this library do not exactly match GitHub's names.

For example, :couplekiss_woman_woman: (:couplekiss_woman_woman:) on GitHub is listed in this library as female_couplekiss.

Maybe an entry like this would work?

  "female_couplekiss": {
    "keywords": ["pair", "valentines", "love", "like", "dating", "marriage"],
    "char": "👩‍❤️‍💋‍👩",
    "category": "people"
    "xref" : {
      "GitHub": "couplekiss_woman_woman"
    }
  }

Hello,

we are using your list at Discourse: https://github.com/discourse/discourse/blob/master/lib/tasks/emoji.rake

Thanks for it!

However, we sometimes have to patch it (code, Fitzpatrick scale...). What kind of PR are you willing to merge? Anything that would match with http://unicode.org/emoji/charts/emoji-list.html ?

For example running_woman is noted as "fitzpatrick_scale": false while it should be true (http://unicode.org/emoji/charts/emoji-list.html#1f3c3_1f3fb_200d_2640_fe0f).

A bunch of new emoji were just released with iOS 9.1 🤘

Hello,

I want to write an application that gets emoji of a text and turns it into words (for blind people or visually impeared people who can't see emoji well, or to people that are not used to internet and don't understand emoji) and I wish to use emojilib. But to do that, I would have to create a hashmap that the key is the char, for instance:

 "grinning": {
    "keywords": ["face", "smile", "happy", "joy", ":D", "grin"],
    "char": "😀",
    "fitzpatrick_scale": false,
    "category": "people"
}

would become:

 "😀": {
    "keywords": ["face", "smile", "happy", "joy", ":D", "grin"],
    "name": "grinning",
    "fitzpatrick_scale": false,
    "category": "people"
}

I thought of creating some kind of script which would update the second file based on the first when the first was updated (When it received a new emoji or something like that). I was thinking of using Python for that, and everytime the emoji file was updated, this script should be run (or run it during NPM install)... What do you think? Plus I would add new functions to get text based on emoji.

A friend suggested that the keyword workflow could be more streamlined and moved away from the heaving friction flow of opening a PR and a manual review. Imagine something like

• propose an English keyword for 🫥
• community (GitHub users?) get to vote on whether that keyword is valid
• once a keyword gathers enough vote maybe someone (well me I guess) still do a final gut check
• one button click we can use github actions to put that keyword into the json file
• another github action to publish

questions

• how many votes is enough votes?
• would this get too noisy?
• is that gut check needed?
• need #194 before this can happen

This seems like something https://github.com/muan/emojilib/discussions can be used for.

https://github.blog/changelog/2021-06-29-github-discussions-events-available-on-github-actions/

I was wondering if you already thought about localization/internationalization.
There is already a PR (#6) for that. What do you think about this approach?

I think it might be complicated to maintain. If you want to add/change an emoji you have to do it in n files.
My idea would be a format e.g.

emojis.json

[
  {
    "char": "🍍",
    "name": {
      "en": "emoji_name",
      …
    },
    "keywords": {
      "en": ["keyword1", "keyword2"],
      …
    },
    "category": {
      "en": "emoji_category",
      …
    }
  },
  {
    …
  }
]

Here you could maintain one file and parse it in a build process etc. to create the different files for each language (emojis_en.json …) in the format like it is now.

What do you think? 😊:v:

Almost all of the country flags use their name as the key in the emojis object. However, a small handful of 'major' countries, just use a two character code, like Japan, United States, United Kingdom etc. Because of this, theres no way to give the US emoji the full name. It does have "united", "states" as two separate key words (amongst others). Japan is another example that doesn't include the full name at all.

What system should be put in place, for example, if the emoji is a flag, the first keyword is always the full country name (even if it includes spaces)?

"jp": {
--
  | "keywords": ["japanese", "nation", "flag", "country", "banner"],
  | "char": "🇯🇵",
  | "fitzpatrick_scale": false,
  | "category": "flags"
  | },

Do we we really need the keys array? It can be easily obtained using Object.keys(emoji). 💭

Currently I causes some trouble because I want to check if a word is emoji, so emoji[myWord] will fail for myWord === "keys" (it's not an emoji object but an array).

Looks like it's anyway causing some problems on the Emoji Searcher page:

I'm almost sure there is no :keys: aliased with :-1: but it's just an issue because of the keys object.

So, is the keys array really needed? I would vote to be removed. 🎈

Many emojis in the emojis.json list their category name (or a piece of their category name) as a keyword. In the same way that part of their description as a keyword (as the test enforces), should these be removed as redundant information as well?

A few examples:

  "mouse2": {
    "keywords": ["animal", "nature", "rodent"],
    "char": "🐁",
    "category": "nature"
  },

There are many animals with "nature" and "animal" included in keywords, and if the category is renamed to "Animals and Nature" will be really redundant. Though, having "animal" as a keyword might distinguish it from non-animal-nature-things (facepalm).

  "family": {
    "keywords": ["home", "parents", "child", "mom", "dad", "father", "mother", "people", "human"],
    "char": "👪",
    "category": "people"
  },

Also in this case "people" indicates more than one person moreso than the category, so it's ambiguous here too.

Let me know what you think.

Need to add these https://blog.emojipedia.org/ios-11-1-emoji-changelog/ :)

Likely dependent on muan/unicode-emoji-json#18

#160 (comment)

https://github.com/muan/mojibar/blob/3a1dac0998202e8425a63acb37da82aa7d6385f9/app/search.js#L225-L229

For example there is an entry for "iran,", "micronesia,", "moldova,", "macedonia,", and "tanzania,".

I was reading through it and wondering where the data was from? Mechanical Turk? Another website?

It would be nice to be able to add keywords in a given category (or categorize keywords) like noun, verb, adjective, adverb, ...

I need to streamline this process. Probably need to do some research into how other people do this.

UPDATE Process currently:

1. Prebuild for simplemap.json and commit if needed
2. Update version number in bower.json and package.json
3. Commit changes
4. git tag
5. git push --tags
6. Create release on GitHub
7. npm publish

I wish these steps can be reduced to a button as we merge in tiny updates like keyword additions. 😂

"pleading": { "keywords": ["face", "begging", "mercy"], "char": "🥺", "fitzpatrick_scale": false, "category": "people" },

I used emojilib to make this project and I thought of some ideas for features I wanted. These features would require restructuring the way the emoji/keyword relations are stored and adding some information that isn't present currently.

Problems I'm trying to solve:

1. It would be nice to have emoji sorted by search relevance (e.g. 😸 is more similar to "smile" than 😎).
2. Searching for emoji by keyword could get slow if it's necessary to iterate through all emoji to find ones that match.

My ideas for solutions:

• Store keyword->emoji relation
• Store relevance rank between keyword and emoji
• Use a build step to allow relations to be represented in multiple ways through different modules (e.g. keyword->emoji map in one and the existing structure in another)

An example:

// keyword.json
{
  "smile": [
    {"emoji": "smile", "similarity": 95},
    {"emoji": "grinning", "similarity": 84},
    {"emoji": "sunglasses", "similarity": 40}
  ],
  "dog": [
    {"emoji": "dog", "similarity": 95},
    {"emoji": "dog2", "similarity": 92},
    {"emoji": "poodle", "similarity": 75},
    {"emoji": "feet", "similarity": 30}
  ]
}

// category.json
{
  "people": [
    "grinning",
    "grin",
    "joy"
  ]
}

// emoji.json
{
  "smile": {
    "char": "😄"
  },
  "grinning": {
    "char": "😀"
  },
  "sunglasses": {
    "char": "😎"
  }
}

These files could be compiled into emojis.json to allow backwards-compatibility.

I thought about making a library structured somewhat similar to this and basing the initial data on emojilib, but keeping it up to date would require adding similarity rankings for new additions to emojilib.

What do you think about a library like this and would it make sense to add this information to emojilib?

By observing https://www.wikiwand.com/en/Unicode_symbols one could possibly see that not all image symbols in Unicode are included within the "Emoji" set. With considerations to other libraries mainly targeting the creation of Emoji fonts, I would like to request for an expansion of the library.
e.g.

• https://www.hotsymbol.com/star-symbols
• https://www.hotsymbol.com/music-symbols
• https://www.hotsymbol.com/heart-symbols

I've been using the Vulcan Salite emoji for quite a while and can't seem to figure out what the text version of the emoji (for example is :octocat:) is.

I've come up with for emojis.json

"vulcan-salute": {
    "keywords": ["vulcan", "salute", "star", "trek", "sprock", "leonard", "nimoy", "hand", "nerdfighters"],
    "char": "🖖🏽",
    "category": "people"
  },

but don't know the text version. Can anyone help and add this into the library?

This is more of a suggestive pull request to move to TypeScript or just set up a definition file. I would be happy to make a PR for this myself, but I want to hear your stance on typings first - if you don't want this, I'll make a PR on DefinetlyTyped instead 👍

I sometimes don't want to use emojis that I know are too new to be supported on certain devices. For example unicorn might not be too new for my situation, but maybe duck is.

The Unicode version isn't a perfect indicator of age/newness, but it seems like a decent one.

For practical usage, it might be useful to reference a credible source of Unicode. e.g. https://emojipedia.org/pride/

Hi @muan, as I saw in #6 and #9 you said we should just create a emoji-[locale].json file.
How does the index.js file should handle those in the future ?

It would be nice to have support for the Fitzpatrick scale modifiers for diversity. (Even though support is far from ubiquitous, with Chrome notably lagging behind in implementing this.)

The Fitzpatrick modifiers are used to add diversity to emoji. For example, 👦🏽 should display a boy with FITZ-4 applied.

Since not all emoji support the FITZ modifiers, this is not a trivial change. But I think it would be a nice addition to have.

Can we get rid of "custom" emojis? Or at least put them in another file so we can pick around them. It feels like garbage. The character is null. Thats lame.

https://github.com/muan/emojilib/blob/bd543325f3becf1146eb361c30aa0e3f1ce1195b/emojis.json ref: #24

Thanks to @yoshokatana & @wbinnssmith "Smileys & People" + "Animals & Nature" are 99% done. The 1% is just the 14 different types of families which I was too lazy to add after re-ordering all of them. 😬

master is currently sort of usable, i just need to cut a 2.0.0 version for it; however I would really like to get all the new emoji in for the 2.0.0... Hopefully that wouldn't be too long. ⁉️

So if anyone's interested in helping it'd be awesome! And let me know here if there are any questions.

TODOS:

• 14x(left) people
• 67x food_and_drink (@muan)
• 57x activity (@muan #42)
• 115x travel_and_places (@muan)
• 178x objects (@muan)
• 269x symbols (@muan)
• 247x flags (@jasonrudolph #41)

✌️

Hi!

I used your lib to replace emoji titles with real emojis, for example :wave: to 👋🏻 .
In version 2.4 there was a map name:metadata but now I can't see a way on how to find emoji by name

Any suggestions?
Thanks in advance