Is storing files in Slack emojis a bad idea? Maybe. Let’s do it anyway!
summary
A file system is implemented by encoding filesystem objects into Slack Emojis and managing them via the Slack API, Python, FUSE, and CBOR2; 116,000 custom emojis yield about 3 GB of storage and each emoji holds roughly 40 KB so files split into chunks and every update creates a new immutable root snapshot. Performance is glacial (many API calls, rate limits), but it works end to end — it even ran Doom in about 4 hours and produced thousands of emoji objects for a single install.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:12Building a file system in Slack emojis
- 3:38Slack emoji storage details
- 4:23Factorio floppy disk inspiration
- 6:05FUSE and file system basics
- 8:09Emoji file system structure
- 11:39Encoding data into emojis
- 14:45Editing emoji-based files
- 16:48FUSE integration
- 17:53Performance and limitations
- 18:56Running Doom and install time
- 20:00Live demo
- 21:02Is this a bad idea?
- 22:06Q&A
related talks
10m88 files a second - running Flappy Bird inside macOS Finder!
30mEmoji, Web Components, and Art
40mSamsung AR Emoji Studio: Create and Market New Avatars
47mLive Emoji Challenge
29mFound Font Family
20mUsing psql to \watch Star Wars And other silly things!
23mDisney and the Creation of Samsung AR Emoji Studio
11mSave Icons! In Real Life?! (My Love of the Floppy Disk!)