Who Owns "Open Source"? Meta's Llama 4 Just Made the Fight Impossible to Ignore

A post near the top of r/LocalLLaMA this week put it plainly: "I'm done explaining to clients why Llama isn't actually open source." The comment has the particular exhaustion of someone who has had this conversation too many times — not angry, just done. It's the mood that makes Llama 4's launch feel different from previous rounds of this argument, even though the argument is structurally identical to the ones Meta has weathered before.

Nature published a call for researchers to "reclaim" the term. The Financial Times declared we're still "a long way from truly open-source AI." PCMag ran a headline saying models from Google and Meta "may not be truly open source." These pieces appeared in the same news cycle, which matters — not because any single outlet has the power to redefine industry vocabulary, but because three credentialed institutional voices arriving at the same conclusion simultaneously is qualitatively different from the grumbling that's been a constant low note in developer communities for years. Meta can absorb a Reddit thread. Absorbing Nature and the FT in the same week costs more.

Practitioners on Reddit are adding a specific technical grievance to the usual definitional one. The mixture-of-experts architecture in Llama 4 has generated its own layer of skepticism under the headline "Meta's MoE Mistake," circulating through r/LocalLLaMA and adjacent communities where people are actually running inference and discovering the gap between benchmark performance and what will realistically run on their hardware. The open-weights frustration and the MoE skepticism are reinforcing each other: the model isn't fully open, and — this crowd is arguing — it may not even be the architectural leap it was marketed as. That combination is harder to shake off than either complaint alone.

Two quieter threads are doing real work at the edges of this conversation. arXiv has been accumulating preprints on small language models achieving domain-specific competence — medical textbook training, specialized reasoning — and the energy in that work feels noticeably different from the flagship-model churn. The researchers publishing there aren't waiting for Meta to open something; they're building differently. The other thread is the IEEE Spectrum story on Llama being made available to the U.S. military. "Open for defense contractors" and "open for humanity" are not the same claim, and the discourse hasn't fully processed what it means that both can be said with a straight face about the same model.

The optimists exist and they're not wrong about everything. On YouTube and X, the consumer-facing story — fast inference on GroqCloud, local LLMs on Android — is being received with genuine enthusiasm, and that enthusiasm reflects something real: these models are more accessible than what existed two years ago. But "more accessible than before" and "open source" are distinct claims, and conflating them is precisely what's producing the fracture. Bluesky's AI research community has found a way to hold both — celebrating the architectural ambition while acknowledging the caveats — but that position requires a level of technical nuance that press releases are not designed to communicate.

The OSI's formal definition excludes most of what the industry calls open source AI, and it now has Nature and the Financial Times implicitly on its side. That coalition won't rewrite Meta's licensing terms, but it can make "open source" expensive to misuse — expensive enough that "open weights" eventually becomes the industry's preferred phrasing, not because anyone conceded the argument, but because the reputational cost of the fight keeps rising. That's not a victory for the r/LocalLLaMA developers who've been making this case for three years. But it may be the outcome they get.