Real-Time Streaming of Every Emoji Posted as a Comment to

Let's say we want to find every emoji as it's posted to Reddit. First, we'll define what an emoji is. The Unicode Consortium keeps their data lists avaliable. We'll bring them in via a JSON file. The file has descriptions and other things we don't need so we'll clean the data a bit and store it in an efficient Set. If we're checking whether a character is or isn't an emoji over 5k times a second we'll need the O(1) look-up time!

import json
with open('emojis/emoji.json', encoding='utf8') as emoji_db:
cleaned = filter(lambda e: 'emoji' in e, json.load(emoji_db))
emojis = set(map(lambda e: e['emoji'], cleaned))

Emoji Streamer

To check every Reddit comment as it comes into existance we'll use PRAW (The Python Reddit API Wrapper). It's the defacto standard for interacting with the Reddit API. It's well documented and straightforward to use.

import praw
client_id = os.environ['CLIENTID']
client_secret = os.environ['CLIENTSECRET']
reddit = praw.Reddit(client_id=client_id,
user_agent='emoji-tracker v0.1')
while True:
for comment in reddit.subreddit('all').stream.comments():
for char in comment.body:
if char in emojis:
print(char, flush=True)
except Exception as e:
print(e, file=sys.stderr)

Here we set up PRAW with our Reddit app's ID and secret. Once we have a Reddit instance, we can start scanning. PRAW will get all the comments while managing the API limits for us. At around 300k characters per minute, it's quite a lot of data for a human to comprehend but it's peanuts for a PC as long as it's setup properly.

Let's pipe any emojis we find out to stdout making sure to flush every print so we don't leave any hanging. Emojis sometimes come in slowly, and one at a time -- we want to make sure that our UI is updating as soon as possible to hold the user's attention for a little longer (for those users who enjoy watching a string of emojis grow and grow).

By the way, which of you is posting 40 crabs at a time and why!?


We'll catch these emojis in Node.js. express/express-ws was chosen so that we can simply host our static files while also making an emoji stream avaliable over a WebSocket. The file will be called as a child process. Let's attach some event listeners to catch the emojis as they are sent to stdout.

/* Whenever new emojis are ready, clear up CLOSING/CLOSED connections
while sending emojis to the remaining clients */
const emojiStreamer = process;
emojiStreamer.stdout.on('data', (emoji) => {
emoji = `${emoji}`;
Array.from(clients, client => {
if (client.readyState > 1) {

We convert the data into a String, clean up closed or closing connections, and disperse the hot-off-the-press emojis. If the emojis were posted more often, say ten times more often, then it would make sense to place them into groups before passing them around (in Node.js or Python, wherever the closest bottleneck is).

Over in Front End Land, we let the user know when they're connected and let loose the fresh emojis. The reason we split('\n') here is to fix some unsyncing issues with the stdout pipeline -- a flaw in our design but necessary for rapid prototyping.

ws.onopen = () => {
status.innerHTML = 'Connected āœ”ļø';
ws.onmessage = (emojis) => {
// Multiple emoji may arrive delimited by a new-line char
emojiList ='\n');
emojiList.splice(emojiList.length - 1);
emojiList.forEach(emoji => {

Did you know that there is no consensus on what the plural of emoji is? Let me know at @healeycodes if you've been wincing at my usage of emojis!

This project is open sourced at Emoji Streamer with Travis CI counting emojis and making sure our tests pass šŸ‘