This is what an export control looks like when it collides with an open ecosystem. The point of restricting a capability is to deny it to rivals. But capabilities are not only embodied in specific products — they are embodied in published research, in open weights, and in a global community of people racing to reproduce whatever is hot. Restrict the product, and you can accelerate the open alternatives and motivate the reconstruction effort, the opposite of what was intended. The competitive map is being redrawn in real time, and not obviously in the direction the policy hoped for.
The caveats matter, because the triumphant version of this story oversells it. First, "tops the download chart" is a measure of attention and availability, not of real-world dominance — a model can be the most downloaded thing on a hub while still trailing the best closed models on the hardest tasks, and the most eye-catching claims about these models come from their makers and their fans, not from neutral referees. Second, a model being free to download is not the same as it being usable. The largest of these systems are so big that running them at full strength requires a rack of expensive specialized chips almost no individual owns, the exact gap we described in the piece on open licenses and closed hardware. The hardware to run the best open models is itself subject to export controls. So the real picture is messier than "the ban backfired." Policy aimed at the software layer is leaking around the edges through open weights and a determined community, while a separate set of controls on the hardware layer still bites. The map is being redrawn — just not cleanly, and not yet in anyone's favor.
Originally published on Ground Truth, where every claim is checked against the primary source.