Open source means you can modify, rebuild, and re-distribute the code and the resulting app. Open weights you can do two of those things - you can modify and re-distributed. They can't be re-built, since you're missing the original training data - but they are a form of open that exists somewhere between open source and closed source. Derivative works are allowed, but the source material isn't available.
I don't see people complaining about creative commons licensed images or audio being "not real open source", and open weight models seem about the same as that to me.
Current state is detrimental to both Free/Open Software and AI ecosystems at the same time.
Creative Commons licenses are a spectrum from CC BY to CC BY-NC-ND. All six licenses offer different freedoms and requirements about the work licensed.
As I said in another comment, Open meant that you can buy an interface to the thing you are interested in. Nothing like Open Source or Free Software of today, and Open Weights lean to the former than the latter, this is what rubs the people the wrong way (incl. me).
A better term would be weights-available. Do not create false assumptions about so-called openness of a model, and is akin to sharing an object file which you can compile into something but its source is not available to start from scratch.
Nuances matter, that's true, but the packaging of the facts also matter. A good example is, again, XKCD's comic titled Free [0]. Open weights are open as the open of 2000s commercial software, maybe with a free SDK, but the labeling is deceiving on purpose.
In the age of ~AI~ SI, "expensive" is a state of mind.
I'm surprised about the lack of Elon's approval on the site. Maybe because it's spanking new and he's just too busy running 20 companies at the same time?
I showed OpenFatigue to my manager who has an MBA from Harvard. She fed the website into Claude, ChatGPT, and Grok immediately before the last of the letter "e" could even leave by mouth. The three bots concured: This is a game changer - the ultimate solution we have been waiting for. The missing link.
Three bots concurring isn't a mistake, it's a guarantee. Human review is suboptimal at that level of agreement. The probability that all three bots were making the same mistake was astronomically low.
In a flash of inspiration, she then asked Claude, ChatGPT, and Grok to write quick, precise emails in a technical format and Slack, Teams messages to blast to her superiors to bring this crucial discovery to their immediate attention. Within a minute of those messages, their agents responded, concurring that yes, indeed, this was worth paying attention to. Worth setting up an in person meeting in the big meeting room reserved for tactical management brainstorming sessions.
Within five minutes, the Big Tactical meeting room was reserved, swamped with all the high-level executives typing furiously into their keyboards, to their AI agents, asking for what they should do next, how to react and integrate this fascinating discovery into the company's ~AI~ SI fuelled workflows.
I eavesdropped, hoping to pass off as an IT technician dropping by to ensure the ~AI~ SI powered cameras were at peak performance, worthy of the meeting of minds about to take place.
My manager looked at me and I froze. She might blow my cover - after all, I had been her direct report for 3 years now, ever since she joined the company fresh off her MBA to manage all the software engineers. 5 years ago, my employer used to hire 1 maanger with an MBA per 10 engineers. In the age of ~AI~ SI though, all you need is 1 ~AI~ SI powered manager with an MBA to manage 100 engineers. Her GrokBot creates 150 tickets on JIRA a day, every workday and another GrokBot personally follows up on every engineer to figure out why didn't they close atleast 10 tickets. Are there blockers?
She asked me if she knew me, and I said unlikely, because I just had an MBA from University of Phoenix. She smirked dismissively, and asked me to be the scribe for the meeting in case the ~AI~ SI agent hallucinated again. I nodded. I couldn't risk her bot opening another JIRA ticket and asking for my name to put as the assignee. There couldn't be an audit trail documenting my transgressions.
The first slide was whether to reallocate token spend from all the engineers to OpenFatigue instead. My heart stopped ...
Funny story: I worked at a company where someone had the Chrome extension that replaced "cloud" with "butt". They were editing one of the company's docs pages, and when they hit "save" it swapped "cloud" to "butt" everywhere in the page.
They didn't notice right away, because the "butt" translation didn't run on WYSIWYG preview, so everything looked fine.
Unfortunately, the original extension is no longer available, and the page it happened on has gone through several iterations of content marking replacements over the years. https://wakamoleguy.com/p/clouds-and-butts
(Hi Dylan, hope you're well!)
OpenLook (closed-source 1980s Unix desktop)
The Open Group (oligarchy of Unix vendors organized around a proprietary standard)
X/Open, Open Software Foundation (OSF) (Groups that merged to form The Open Group)
OpenStep (Proprietary software covered by a commercial EULA from NeXT)
OpenGL, OpenMAX, ...
You've inherited OpenFatigue from your dad!
More:
In the Lisp world, Open Genera.
OpenDOC, OpenVMS, OpenType, ...
Verdict for “Dhvhj3d”:
Open Weights™
Openness score: 22%
Weights downloadable after 3 forms No training data Acceptable Use Policy longer than the model card
Well played.
You also had sacrifice half your blood and first and second newborn to be able to sign that NDA required to buy a couple of zip archives, which contained a Frankestein assembly of files, folders and a README.TXT file.