An illustrated person looks up at a large hazard symbol, which has a character representing data science and AI ‘standing’ next to it.

Amidst the drama around the WordPress project at the moment (which is, in my experience only a public version of what goes on behind the scenes of any major Open Source project) I was interested in a post by Matt Mullenweg.

I’ve been using Llama 3 on projects where it wouldn’t be appropriate to use OpenAI’s offerings, but I should have known that, given it’s from Meta, there would be some shenanigans. And so it proves.

I’ll not share the rest of the post, given Matt’s ‘ecosystem thinking’ seems a bit disingenuous given the spat he’s engaged in, but this bit shocked me.

Open Source, once ridiculed and attacked by the professional classes, has taken over as an intellectual and moral movement. Its followers are legion within every major tech company. Yet, even now, false prophets like Meta are trying to co-opt it. Llama, its “open source” AI model, is free to use—at least until “monthly active users of the products or services made available by or for Licensee, or Licensee’s affiliates, is greater than 700 million monthly active users in the preceding calendar month.” Seriously.

Excuse me? Is that registered users? Visitors to WordPress-powered sites? (Which number in the billions.) That’s like if the US Government said you had freedom of speech until you made over 50 grand in the preceding calendar year, at which point your First Amendment rights were revoked. No! That’s not Open Source. That’s not freedom.

I believe Meta should have the right to set their terms—they’re smart business, and an amazing deal for users of Llama—but don’t pretend Llama is Open Source when it doesn’t actually increase humanity’s freedom. It’s a proprietary license, issued at Meta’s discretion and whim. If you use it, you’re effectively a vassal state of Meta.

When corporations disingenuously claim to be “open source” for marketing purposes, it’s a clear sign that Open Source is winning.

Source: Ma.tt

Image: Managing Data Hazards by Yasmin Dwiputri & Data Hazards Project