| ▲ | maxloh 2 hours ago |
| > 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. [0] 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. [0]: https://huggingface.co/mistralai/Mistral-Large-4-1T-A52B/blo... |
|
| ▲ | fuddle an hour ago | parent | next [-] |
| This is the new OSI Open source definition for AI models: https://opensource.org/ai/open-source-ai-definition Mistral Large 4 is definitely not open given the "use for any purpose without having to ask for permission" requirement. |
| |
| ▲ | maxloh an hour ago | parent [-] | | Not really. That definition also requires the training code and training data composition to be open-sourced. No major Chinese or Western labs satisfy these requirements. The only vendors I can think of that do are Nvidia and Allen AI. | | |
|
|
| ▲ | matt3210 12 minutes ago | parent | prev | next [-] |
| > If the Licensee or any of its affiliates operates a Model as a Service business, the Licensee must enter into a separate Put a JEV on the output to filter out responses that might show its Mistral Theft is the AI way |
| |
| ▲ | doctorpangloss 5 minutes ago | parent [-] | | It doesn't really work like that. There are "keys" where you train in a specific response to a variety of queries. You can't really fine tune that away either. |
|
|
| ▲ | maxloh 2 hours ago | parent | prev | next [-] |
| We are now at the mercy of labs to provide frontier models as open-weight. Now that even some Chinese labs are releasing their models as weight-available, what stops them from prohibiting certain internal uses of new models? What about public chatbots? Open models we have now will become obsolete within a few years. Imagine a world where our last open models were from the GPT-2 era. I believe we need truly sovereign models, not in the Western sense, but from a community perspective. We need a model line that stays open-source across generations. |
| |
| ▲ | lisplist an hour ago | parent | next [-] | | The problem is the massive amount of money, data, and talent to produce anything remotely competitive. Ideas have been floated about distributed training, but training requires insanely fast interconnect between nodes making it impossible with the current methodologies we have. Now if you mean funded at a national level, that seems more doable so long as the training runs are centralized in big DCs. | |
| ▲ | wolttam an hour ago | parent | prev | next [-] | | There's always going to be some nerds out there that want to make and release a model as open, and share their knowledge along the way. I'm not too concerned. The fear you're sharing has been shared since day 1 of open-weight models and it has yet to come to fruition. Further, regardless of what any of these labs license their model as, the end user who has downloaded the weights can still use them for virtually any purpose (synthetic data, classification, etc) as much as they want and there is no way to reasonably enforce a license on those outputs. So even if you can't run a service using this model's weights (without a license), the weights still do provide utility for training new models with any other license. *Edit, responding to the replies: Constraints give rise to ingenuity. Who knows how we'll be training models in the future. Hopefully in a distributed fashion, maybe with some kind of consensus-driven training dataset selection. Crowd funding, etc. There's too many people that want this, and the knowledge on how to do it is out there (many times by now) | | |
| ▲ | crimsoneer an hour ago | parent | next [-] | | I think this is a quite optimistic view... releasing a SOTA model is a collosal capital investment, and unlike free software, it's not iterative - you can't make a small model and improve it one step at a time, you need to risk the whole load of cash, expertise and GPU time up front. It's only happening now because labs have bucket tons of VC cash to burn and need a big public flex to raise more cash, or because they're subsidised by the Chinese government. I'm not massively confident either of those will stay true forever. | | |
| ▲ | joelthelion 4 minutes ago | parent [-] | | I'm not an expert, but maybe updating an existing open-weights model to give it up to date knowledge would be more tractable? |
| |
| ▲ | poszlem an hour ago | parent | prev [-] | | Unless "some nerds" means "billionaires" - they may want to release new models as open source, but they will not have enough money to train a worthwhile model. |
| |
| ▲ | wraptile 27 minutes ago | parent | prev [-] | | With distillation being so effective I do wonder whether we can just crowd source open alternatives. |
|
|
| ▲ | Izmaki 7 minutes ago | parent | prev | next [-] |
| The weights are open, meaning publicly accessible, but you can't have a business profit off of them without paying for a license. That sounds fair and accurate. HashiCorp has the same business model for their products: you are free to use them even in a business, except if your business is a competitor of their own cloud solutions. |
| |
|
| ▲ | RobotToaster 43 minutes ago | parent | prev | next [-] |
| Isn't it basically settled that model weights can't be copyrighted as they don't pass the threshold of originality? |
| |
| ▲ | sigmar 26 minutes ago | parent | next [-] | | yes. I don't understand why people are saying these licenses matter. Much of these terms are likely unenforceable. | |
| ▲ | p_l 42 minutes ago | parent | prev [-] | | In EU especially it's already settled, afaik, as are direct model outputs |
|
|
| ▲ | 3abiton 42 minutes ago | parent | prev | next [-] |
| Releasing weights even with permissive license, doesn't technically make it "open-source", unless all the method, data and technical inner working to do it is also released. Otherwise, it's just a binary floating in the wild, even if it's under MIT. |
| |
| ▲ | abdullahkhalids a minute ago | parent | next [-] | | I would compare them more to media released under the creative commons license. For example, you can record yourself playing different instruments, singing, and making other sounds. Then you can go combine all these recordings into a song, and you release the song under a CC license. The CC licenses framework does not demand that you also release the component recordings. But the released song can be remixed by someone else. (Not making a value judgement, just making an equivalence). | |
| ▲ | pdpi 17 minutes ago | parent | prev [-] | | It's effectively shareware. What was old is new again. |
|
|
| ▲ | terabyterex 22 minutes ago | parent | prev | next [-] |
| Unless, i am missing something they haven't claimed open source anywhere. none of them have claimed open source. open weights has never meant the same thing as open source. |
|
| ▲ | ShinyLeftPad 2 hours ago | parent | prev | next [-] |
| Yep and it's the same for Meta's "open" models which you omitted from the list. Is there actually a competitive proper actually open model? |
| |
| ▲ | maxloh an hour ago | parent | next [-] | | I believe Meta's models were never truly frontier in the way Qwen, Kimi, etc., compare to Claude or ChatGPT. Correct me if I am wrong. | |
| ▲ | crimsoneer an hour ago | parent | prev [-] | | Inkling, Nemotron Super, Beam Reflection (and of course Kimi, Qwen, etc) | | |
| ▲ | ShinyLeftPad an hour ago | parent | next [-] | | > (and of course Kimi, Qwen, etc) Latest versions of Kimi, Qwen, GLM aren't open, you need to pay them for commercial stuff and comply with PRC laws | | |
| ▲ | crimsoneer 32 minutes ago | parent [-] | | Oh, I'd missed this, that's a shame! But yeah, Inkling + Reflection are properly open and quite good. |
| |
| ▲ | an hour ago | parent | prev [-] | | [deleted] |
|
|
|
| ▲ | Rapzid an hour ago | parent | prev | next [-] |
| I don't recall their being a huge backlash to elasticsearch ELv2. Mostly people seemed receptive to blocking the major cloud providers from mooching off the project, and the need to protect their revenue. People need to make money. This provider exclusion licenses though.. In a world were someone can point an LLM at your software to launder it.. Not sure what's going to happen. |
|
| ▲ | FooBarWidget 23 minutes ago | parent | prev | next [-] |
| To the people who demanded completely open source licensed software, or that complained about "they shove Wayland/systemd down our throats", I've said many times that this is a supply/demand problem. Open source licensed software exists because there is a lot of excess software production capacity, e.g. there are many volunteers. Non-systemd distros are rare because such production capacity is low, e.g., there are few volunteers willing to do this work. To those people I've said: stop complaining about others not doing it for you, if you so want your non-systemd distro or FOSS-licensed whatever, you gotta do it yourself and contribute to the community, or fund an effort. I got super angry reactions. Now, the same thing is happening with open weights models, but in on a much more extreme scale. They exist because of excess capacity for whatever reason, and they will cease to exist when this excess capacity reduces. There is no use complaining about something not being open weights. What is productive is funding an effort. Unfortunately, most complainers want others to do things for them, for free. |
|
| ▲ | ekianjo 23 minutes ago | parent | prev | next [-] |
| No, it's open-weights, as in you can inspect them. This is not Free Software. |
|
| ▲ | vrganj 2 hours ago | parent | prev [-] |
| If they want to be open source, they also need to, y'know, open the source. Weights are more like an executable binary. The source is the training data etc |
| |
| ▲ | whatisthiseven an hour ago | parent | next [-] | | I don't understand this demand. Isn't the training data likely petabytes in size? You want that to be available? I imagine just the index (name,date,source) is a terabyte or two. As the training data is every written thing they can get their hands on, right? And wouldn't making that "open source" violate every license that the original data has? You can't release someone else's work. Unless I have a misunderstanding? | | |
| ▲ | simias an hour ago | parent | next [-] | | I absolutely want that to be available. The only way to make sure that a model was trained without hiding weird biases and backdoors is to monitor this process. It also allows anybody (with the hardware resources) to experiment with the model and how it's trained. Will most people want to do that? No, but most people also don't want to recompile their own kernel, that doesn't negate the value of Linux being FOSS. I hope that, in the long term, I'll be able to use competitive, completely open models in the same way that I can run Linux on my computer. You're completely right that the licensing of the training data is a big issue though (and I would argue that it should be a much bigger issue right now, even for closed models). I hope that eventually our understanding of the tech will let us build competitive LLMs using purely public domain/Creative Commons-style training data. I realize that we have a long way to go... but that's a very worthwhile goal IMO. | |
| ▲ | NewJazz an hour ago | parent | prev | next [-] | | I don't usually compile my kernel from scratch, but I'm very glad that the source is open. | |
| ▲ | Tepix an hour ago | parent | prev | next [-] | | How else do you want to reproduce a model if you don't have the training data? | | |
| ▲ | Catloafdev an hour ago | parent | next [-] | | You plan to rent GPU-hours to train a from-scratch model yourself, with the exact same training data? What are we talking about? | |
| ▲ | brainwad an hour ago | parent | prev [-] | | Just reproduce it? Copy the weights. What I think you want is the ability to improve it, to make what in copyright would be called a derivative work. |
| |
| ▲ | birdsongs an hour ago | parent | prev [-] | | > And wouldn't making that "open source" violate every license that the original data has? You can't release someone else's work. Tangent, and not the person you're replying to, but you just independently re-discovered why so many of us despise the AI companies. Because that's what they are already doing. Selling a repackaged form of the stolen work of all of humanity, without credit or payment. |
| |
| ▲ | RobotToaster an hour ago | parent | prev | next [-] | | Hence the difference between open weights and open source. But this is neither. | |
| ▲ | mirekrusin 2 hours ago | parent | prev [-] | | Can you evolve binary like you can post train weights? | | |
| ▲ | Muromec 2 hours ago | parent | next [-] | | You can read and edit binary code just fine, it's much easier with AI too | | |
| ▲ | mirekrusin an hour ago | parent [-] | | Do you have examples you can point to? For example there are more than 100k modified weights on hugging face. | | |
| ▲ | Wheen an hour ago | parent | next [-] | | It's usually against the license to redistribute modified binaries. There are few pieces of software (I cannot think of any) that allow redistribution of modified binaries, but aren't open source. As a result, in practice, the only example I can think of is cracks for pirated software. | |
| ▲ | Muromec an hour ago | parent | prev [-] | | Easy: https://www.nexusmods.com/ |
|
| |
| ▲ | 2 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | teiferer 2 hours ago | parent | prev | next [-] | | Indeed. You can hardly re-create the binary from a suitable source, just like the weights just fell from the sky. But you can change the binary (patch the machine code) just like you can adjust the weights. The comparison is quite apt. | |
| ▲ | NegativeLatency 2 hours ago | parent | prev | next [-] | | Yes? | |
| ▲ | bayindirh 2 hours ago | parent | prev [-] | | The whole reverse engineering and cracking scene is built upon this premise, you know. | | |
| ▲ | losvedir 2 hours ago | parent | next [-] | | Calling it a "cracking scene" shows the different, though. Open weight models are intended to be used this way. | | |
| ▲ | simias an hour ago | parent [-] | | Hotpatching binaries used to be extremely common. It's less so in the modern age but mainly because we moved software to higher levels of abstractions, virtual machines and interpreters, and also because rebuilding even a massive project from source is achievable on commodity hardware. You can still see various hotpatching schemes being developed, for instance to allow partial recompile of the sources while developping. If in 2080 we can retrain Opus 129.5 directly on dev machines from scratch in <2h, I doubt many will bother messing with the weights directly. |
| |
| ▲ | Muromec an hour ago | parent | prev [-] | | don't forget game modding. it's the only way it even works | | |
| ▲ | mirekrusin an hour ago | parent [-] | | Post training is general purpose method, same process that original authors used - that's not the case with binaries. | | |
| ▲ | Muromec an hour ago | parent | next [-] | | I think opening something in the hex editor, changing necessary bytes and saving it is as general purpose as it gets. You usually don't distribute it (I remember they days when it was common however) due to law, so in practice people write code that hot-patches stuff after starting the process. You can also just open gdb and patch the process on the fly when you need to do things. At the end of the day there isn't much hard difference between source code and binary code. By design source code is usually easier to read and write, but it's all syntax sugar and transformations all the way down. | |
| ▲ | bayindirh an hour ago | parent | prev [-] | | RedHat and Ubuntu has kernel hot-patching. That's a case with binaries. | | |
| ▲ | mirekrusin an hour ago | parent [-] | | You're conflating runtime patching with continuing development. Post training directly evolves existing model weights using the same optimisation process that created them. Software: source code -> compiler -> binary Models: weights + training data + optimizer -> updated weights Ie. binary is output of the development process. Model weights are both – it's output and it's direct input for further development. |
|
|
|
|
|
|