惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

阮一峰的网络日志
阮一峰的网络日志
Jina AI
Jina AI
GbyAI
GbyAI
D
DataBreaches.Net
人人都是产品经理
人人都是产品经理
Hugging Face - Blog
Hugging Face - Blog
V
Visual Studio Blog
P
Proofpoint News Feed
The Cloudflare Blog
H
Help Net Security
MyScale Blog
MyScale Blog
T
The Blog of Author Tim Ferriss
量子位
博客园 - 聂微东
Apple Machine Learning Research
Apple Machine Learning Research
T
Tailwind CSS Blog
博客园 - 三生石上(FineUI控件)
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
MongoDB | Blog
MongoDB | Blog
Last Week in AI
Last Week in AI
大猫的无限游戏
大猫的无限游戏
小众软件
小众软件
月光博客
月光博客

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
What If You Compressed Your Prompts Into Chinese Emoji? (...
Mei Hammer · 2026-04-27 · via DEV Community

What If You Compressed Your Prompts Into Chinese Emoji? (A Token-Saving Thought Experiment)

Or: what happens when a frustrated developer thinks too hard about token costs


I keep hitting token limits.

Not occasionally — consistently. Every time I think Ive optimized enough, the bill creeps up or the context window fills mid-task. So I started thinking about creative ways to cut token usage. What started as a reasonable question turned into something genuinely unhinged.

The Observation

Somewhere in a Reddit thread about LLM cost optimization, someone claimed that Chinese text uses 30–50% fewer tokens than equivalent English for the same semantic content.

My first instinct: that cant be right. Chinese characters are complex — surely they cost more?

Turns out the intuition is wrong. Modern tokenizers map common Chinese characters to roughly 1 token per character. English looks cheaper per word, but English needs articles (a, the), prepositions (of, in, to), and filler words that carry almost no meaning. Chinese skips all of that.

Same idea. Fewer tokens. The density wins.

The Idea That Got Out of Hand

Once I accepted this was real, my brain immediately went somewhere dangerous:

What if I translated prompts to Chinese before sending them to the expensive model?

English prompt
    ↓  [cheap local model — translate to Chinese]
Chinese prompt  ← ~40% fewer tokens?
    ↓  [expensive frontier LLM]
Chinese response
    ↓  [cheap local model — translate back]
English response

Enter fullscreen mode Exit fullscreen mode

Local models (Ollama + Qwen or DeepSeek) are decent at translation and run on your own hardware — no API cost. The translation overhead is real, but for batch or async workloads, the intuition is: the savings on the frontier model should cover it.

I havent benchmarked this properly. But I like where its going.

Then It Got Weirder

Still in mad-scientist mode: even within Chinese text, emotional expressions could be swapped for emoji. 直冒冷汗 (breaking into cold sweat) is 4 characters. 😅 is 1 token. For high-frequency filler phrases, a lookup table of emoji substitutions could shave off a bit more.

The model would understand it perfectly — its been trained on the entire internet, emoji included.

So the full pipeline becomes:

English prompt
    ↓ translate to Chinese
    ↓ replace common phrases with emoji
    ↓ send to LLM
Response (also compressed)
    ↓ translate back
English response

Enter fullscreen mode Exit fullscreen mode

At this point your logs look like:

"吾 😅 此方案 💡 明日 📅 議之"

Enter fullscreen mode Exit fullscreen mode

Good luck explaining that in a postmortem.

Someone Already Had Half This Idea

I stumbled across caveman — a Claude Code plugin that makes AI respond in caveman-speak to cut output tokens by ~75%. They even have a 文言文 (Classical Chinese) mode, because classical Chinese might be the most information-dense written language ever invented.

Their angle is output compression. This pipeline idea is input compression. Stack them and theoretically youre hitting both ends.

Nobody seems to have done the emoji layer yet. That part might be mine to ruin.

Would This Actually Work?

Honestly — no idea. The translation quality for technical prompts with domain-specific terms could drift. The latency of two extra hops would hurt interactive use cases. And the debugging experience would be truly cursed.

But for the right workload? Batch jobs, background agents, high-volume async tasks where youre paying per token at scale — the logic isnt crazy.

Sometimes the most absurd idea is just one benchmark away from being a real project.


Building agent-chat-gateway — open source infrastructure for connecting AI agents to team chat. Powered and highly motivated by tokens. 🔨