In the silence of the bear market, a platform chose to open its heart. In March 2023, X (formerly Twitter) uploaded the core of its “For You” recommendation algorithm to GitHub—389 files of Scala, Python, and Rust, a digital confession of how it decides what we see. The industry clapped. The regulators nodded. But I, standing in my Singapore apartment with a decade of code audits behind me, felt a familiar ache. This was not a covenant. It was a contract written in invisible ink.
Let me rewind. For years, the algorithm was a black box—a sacred object that creators worshipped and cursed. When X open-sourced it, the narrative was clear: transparency, quality, trust. But as someone who has spent countless nights dissecting smart contracts that promise decentralisation yet deliver control, I know that the code is never the whole story. The real story is in what is left out.
The context is a platform in crisis. User growth had stalled, advertisers fled, and the EU’s Digital Services Act (DSA) was sharpening its knives. X needed a shield. Open-sourcing the algorithm was that shield—a public display of openness that could deflect regulatory scrutiny and restore some faith. But the code they released was a snapshot, not a living system. It lacked the configuration files, the experimental frameworks, and the privacy data pipelines that make the algorithm actually run. You cannot replicate the “For You” feed from this repository. You can only study its ghost.
My soul is a Web3 community founder, and my code has always been my covenant. I have seen too many projects open-source their smart contracts while keeping the governance keys locked in a multisig that only the founders control. X’s move is a mirror of that. The open-source code is a beautiful corpse—it shows the skeleton but not the breath. The real value of X lies in the data: the user interactions, the social graph, the millions of signals that train the model. That data is not open. It never will be.
This is the core insight: open-sourcing the algorithm is a strategic performance, not a structural change. It is a defensive move against regulation, a competitive jab at TikTok’s closed system, and a trust-building exercise for X’s data-licensing business. When you sell data to AI companies like OpenAI or xAI, you need to prove that your algorithm is fair. The open-source code is that proof. But the code is not the product. The product is the data pipeline, and that pipeline remains behind a paywall.
From a technical perspective, the architecture is classic: recall, coarse ranking, fine ranking, re-ranking. The repository uses GraphJet for graph-based recommendations, Elasticsearch for search, and Flock for distributed computing. But the code is a static snapshot, tightly coupled to internal services that are not published. External developers cannot run it. They can only read it. This is not a contribution-friendly open source; it is a display case. The real intention is to invite free code review from the global developer community—a form of crowdsourced bug hunting that compensates for the massive layoffs that X underwent. In the silence of the bear, we heard the truth: the open source was a tool for survival, not generosity.
But there is a deeper layer. X’s move is a message to regulators: “We are transparent. You don’t need to audit us; the whole world can.” This is a brilliant political strategy. By defining the standard of “algorithm transparency,” X can influence the DSA’s implementation. If the EU accepts that publishing code satisfies their requirements, then X has set the bar low. Competitors like Meta and TikTok, which keep their algorithms entirely closed, now face pressure to follow suit. X is not just opening its code; it is weaponising openness.
Now, the contrarian angle. This open source might actually backfire. The code reveals how the algorithm weights different signals—and that can be weaponised. Black-hat operators can study the code to find loopholes for spam or manipulation. The platform has intentionally stripped out the anti-abuse layers, but determined attackers can reverse-engineer the logic. More dangerously, the code contains implicit biases. If a researcher discovers that political content from one side of the spectrum is systematically downranked, X could face a public relations disaster. Transparency is a double-edged sword; it cuts both the shadow and the hand that holds it.
From the perspective of a Web3 builder, this is a cautionary tale. We often equate open source with decentralisation and trust. But open source without data sovereignty, without community governance, is just another form of centralised control. X’s algorithm is open, but the decision to change it remains in one man’s hands. The code is open, but the power is not. Every broken token taught me how to hold value—and here, the token is the algorithm, and the value is trust. You cannot fork X’s algorithm and run your own instance because you lack the data. The network effect of users and content is the real moat, and open source does not touch it.
What does this mean for the future of social media? X has set a precedent. Expect more platforms to open-source their recommendation engines as a defensive posture. But the true test is not whether the code is visible; it is whether the community can verify that the code matches the production system. Without a verifiable compute pipeline, like the ones we build in blockchain with on-chain proofs, trust remains a leap of faith. X has taken a step toward transparency, but it is a step on a tightrope. The audience is watching, and the wind is shifting.
In the end, the open source of X’s algorithm is a reminder that technology is never neutral. It is a contract between the platform and its users, written in code but enforced by power. My code was the covenant, not just the contract—but X’s code is a contract without the covenant of data. Until the data is open, the algorithm remains a altar we can see but not touch. The question for every builder, every creator, every user is this: When we demand transparency, are we asking for the recipe, or the right to cook?