alt Hacker NewsWhere did you get this definition of open weight and who else uses it? The weights are published. Open source is already its own more restrictive category. What would you prefer we call this kind of release?
"Weights available" does not seem to be in wide use and doesn't, to me, communicate anything different than "open weights."
Replies
I didn't make it up, I'm using OSI's definition. Pretty analogous to why BSL or SSPL aren't "open".
It's the same distinction as "open source" vs "source available" (when speaking about source code). It's not that widely in use because few people in the LLM space are diligent enough with IP to make the distinction, but the concept is easily transferable.
I believe there should be a way to distinguish this type of open-weight model from one that you can find hosted by someone else, such as Chinese models.
Just because OpenAI ran roughshod over the broader software community's notion of "open" which once heavily implied free-as-in-software-not-beer, doesn't mean we need to continue this pattern.
Many industries had "source available" without the word "open" for decades, and that was a broadly understood term. "Weights available" would be a reasonable analogue.
For clarity, the Mistral model license is here: https://huggingface.co/mistralai/Mistral-Large-4-1T-A52B/raw...
> 2. If the Licensee or any of its affiliates operates a Model as a Service business, the Licensee must enter into a separate commercial license with Mistral before using the Model or its derivative works for any commercial purpose. The Licensee may contact Mistral, using this form: https://mistral.ai/contact/, to request a commercial license.
> "Model as a Service" means giving a third party access to the Model or its derivative works for inference or post-training by any means (for instance via API or hosted endpoints), in a manner that allows such third party to exercise meaningful control over the inputs, parameters, or training data. This does not include (a) end-user products with model capabilities solely embedded within specific features or harnesses, or (b) mere relaying of requests to models hosted by others.
"Meaningful control over the inputs" is so ambiguous as to be nearly meaningless. Does a model merely summarizing a user's submitted support tickets, give that user meaningful control over the inputs?
Don't get me wrong - I appreciate that Mistral needs to walk a fine line for its own sustainability, and that sustainability is a good thing! And I may just be an old person ranting at a cloud. But "open" used to mean something, back in my day!
Calling this open weight is misleading. That's why we had huge backlash when Redis, Elasticsearch, and Terraform went source-available, right?
Weight-available is a better adjective for this kind of licensing. Same for Qwen, GLM, Kimi, MiniMax, etc. If they really want to be open source, they should pick an OSI-approved license.
"Source available" is already a common term for source code that is provided with a very restrictive license or under regular copyright.