Why social networks failed at language — and what it cost the world.
In 2004, Facebook promised to connect the world. In 2026, it has 3.27 billion monthly active users. A Spanish speaker in Buenos Aires and a Mandarin speaker in Chengdu are both on Facebook. They have never interacted. They never will. Not because they lack something to say — but because the platform they are both on was never designed to let them say it to each other.
This is the language problem of social networks. Every major platform in existence has it. None of them has solved it. And the gap between "connected the world" and "connected the part of the world that speaks the same language" is measured in billions of missed relationships, billions of lost economic interactions, and an internet that is simultaneously global and profoundly siloed.
The translate button is not a solution
At some point in the last decade, every major social network added a translate button. You click it and the post appears in your language. It works well enough for reading a post you stumbled upon. It does almost nothing for the actual problem.
The actual problem is not that you can’t read a single post in another language. The actual problem is that you will never see the post in the first place. Discovery on social networks is driven by the algorithm, which optimizes for engagement, which is highest in your language. You follow people who post in your language. Your feed is populated with content your network engages with, which is content in your language. The translate button is there for the rare case where you manually navigate to a foreign-language post. It does nothing for the 99% of foreign-language content that never surfaces to you at all.
The result is what researchers call language homophily: the tendency of social networks to connect people who speak the same language with each other. This was not an explicit design goal of any social network. It emerged from the architecture. And once it emerges, it compounds — because a network where most of your connections speak one language produces content mostly in that language, which attracts more followers who speak that language, which deepens the cluster.
Why the architecture makes this hard
Social networks were built on a model where content is created once and consumed many times. A post is a post — it sits in a database, and whoever wants to read it reads it. Translation was added as a display-time operation: the post stays in the database in its original language, and a translated version is generated on demand when a user clicks "see translation."
This works for static text. It breaks down immediately when conversation starts. When you comment on a post in Spanish because you speak Spanish, the original poster replies in Spanish. Your reply arrives in Spanish to the Spanish-speaking audience who follows the thread. The English-speaking person who was following along in translation has now lost the thread entirely, because the reply is addressed to someone else and the context of the exchange is no longer available to them.
“Translation as a display-time feature assumes that all the important things happen before the reader arrives. Conversation happens after the reader arrives. This is why the translate button works for posts and fails for conversations.”
The deeper architectural issue is that real-time conversation requires translation to be part of the data layer, not the display layer. Every message in a conversation should be stored in its original language AND made available in every participant’s language, in real time, without requiring any participant to do anything. This is not a harder version of the translate button — it is a fundamentally different architecture.
The commercial explanation
Social networks have not solved the language problem in part because they have not had to. Their business model is advertising, and advertising works better within language clusters than across them. A German-speaking user is worth more to an advertiser targeting Germany if they can be precisely identified as a German speaker who engages with German-language content. Dissolving the language clusters makes the targeting less precise and the ad inventory less valuable.
This is not a conspiracy — it is an incentive structure. Multilingual social graphs are harder to monetize under current advertising models. The platforms have not had sufficient pressure from either regulators or users to solve a problem that, from their perspective, does not need solving. The Spanish speaker in Buenos Aires and the Mandarin speaker in Chengdu are both valuable to the platform in their respective language clusters. The platform has no strong reason to connect them.
What the failure cost
The cost of this failure is mostly invisible because we have never had a baseline of what a world with multilingual social networks would look like. We cannot easily measure the conversations that never happened, the collaborations that never formed, the relationships that never started, the ideas that never traveled.
But we can estimate some of the edges. The science community is perhaps the clearest case: researchers who could be collaborating with peers in other countries are instead collaborating primarily with people who write papers in the same language. Non-English-language research is systematically under-cited not because it is worse but because it is less visible to the researchers who determine citations. The effect is measurable: papers published in English are cited at roughly twice the rate of papers with equivalent scientific value published in other languages.
In business, the effect is even larger. Small and medium businesses in non-English-speaking countries can theoretically sell globally through the internet. In practice, most of them sell locally because all the trust-building infrastructure — reviews, recommendations, community endorsements, relationship networks — is locked inside language clusters. A Brazilian artisan with 10,000 Instagram followers who all speak Portuguese has almost no ability to turn those followers into customers in Germany, even though the product would sell perfectly well there.
What a real solution requires
Solving language in social networks requires rethinking three things that incumbent platforms cannot rethink without rebuilding from scratch:
Discovery without language as a filter. The algorithm must be able to surface content to users regardless of the language it was written in. This means translation must happen before surfacing — before the recommendation engine runs — not after a user has already decided whether to click. It means training discovery on interests, behaviors, and relationships rather than on language-matched engagement signals.
Conversation as a first-class multilingual entity. Every message in a conversation must be immediately available in every participant’s language. This is an infrastructure problem: the translation layer must be embedded in the message delivery system, not bolted onto the front end. It requires making translation fast enough to be invisible and accurate enough to preserve meaning, not just words.
Identity that travels across language lines. On current platforms, your social identity — your followers, your credibility, your history of posts — is largely visible only to people who speak your language. A multilingual social network must make identity portable across language communities, so that reputation and trust can build across language lines rather than being siloed within them.
None of these changes are possible as retrofits to existing architectures. They are foundational design decisions that must be made before the first user joins, not after the three billionth. The existing platforms are too large and too locked into their current models to make these changes. The opportunity belongs to something built from scratch with language at the center, not at the margins.
Babel is building it from the foundation up.
A social network where language is invisible infrastructure — not a translate button you click after the conversation has already excluded you.
Join the Waitlist →Related reading: Translation Isn’t a Feature. It’s a Network Effect. · The Rise of the Non-English Internet · Babel vs Facebook · Babel vs X (Twitter)