Also, all this reminds me of drama in the Skyrim and Minecraft modding scenes, when devs publish stuff under Apache or MIT or whatever.
Then the devs find out they don’t like what others are doing with their code. Drama ensues.
…That’s kinda the deal with permissive licenses. Or posting publicly, like here on Lemmy. People will do things you don’t like with your code or content.
“Look, I wrote this neat highly advanced machine vision thing to help people with accessibility needs communicate with loved ones! ❤️. MIT licensed I guess! Let’s make the world better!”
Raytheon, Northropp, Boeing, Microsoft, three-letter-agencies suddenly fork it as a base for their own “projects.”
Eh, I don’t think it’s hypocritical to contribute to a commons and then get mad when someone comes along and tries to use the commons to undermine the commons.
Like yes, the commons is there to be used… but not to kill the commons.
There are permissive licenses, and then there are copyleft licenses. Permissive licenses go in the direction of “do whatever the fuck you want”. Copyleft licenses are more like “use it for whatever the fuck you want but if you change it give it back to everyone else with the same conditions”. The people who have projects with copyleft licenses are the ones who are (rightfully) pissed about their projects being used to train AI.
Huggingface isn’t violating copyleft licenses here, I don’t think. And research projects that use it, with citations and documentation, wouldn’t either.
Now, if some business comes along and tries to make proprietary code derived from the dataset, that’s where things get hairy. But the people doing that are responsible for the potential violation, not Huggingface.
On the other hand, totally did not see this particular shit coming. I wonder if we’ll see a rash of “permissive, except LLMs can fuck right off” licenses.
No, libraries should remain permissive IMO. Applications can be restrictive if they want to. I just don’t see any point in a copyleft library or framework.
Also, all this reminds me of drama in the Skyrim and Minecraft modding scenes, when devs publish stuff under Apache or MIT or whatever.
Then the devs find out they don’t like what others are doing with their code. Drama ensues.
…That’s kinda the deal with permissive licenses. Or posting publicly, like here on Lemmy. People will do things you don’t like with your code or content.
“Look, I wrote this neat highly advanced machine vision thing to help people with accessibility needs communicate with loved ones! ❤️. MIT licensed I guess! Let’s make the world better!”
Raytheon, Northropp, Boeing, Microsoft, three-letter-agencies suddenly fork it as a base for their own “projects.”
😐
Eh, I don’t think it’s hypocritical to contribute to a commons and then get mad when someone comes along and tries to use the commons to undermine the commons.
Like yes, the commons is there to be used… but not to kill the commons.
https://www.citationneeded.news/free-and-open-access-in-the-age-of-generative-ai/
It’s kind of a tragedy if you think about it
Nah if you’re a massive AI company and you scrape without contribution, you’re a huge piece of shit.
It’s just stealing plain and simple like anything else.
They’re not a small user getting open source software, they’re scraping what is already done to try and make you obsolete.
There are permissive licenses, and then there are copyleft licenses. Permissive licenses go in the direction of “do whatever the fuck you want”. Copyleft licenses are more like “use it for whatever the fuck you want but if you change it give it back to everyone else with the same conditions”. The people who have projects with copyleft licenses are the ones who are (rightfully) pissed about their projects being used to train AI.
Huggingface isn’t violating copyleft licenses here, I don’t think. And research projects that use it, with citations and documentation, wouldn’t either.
Now, if some business comes along and tries to make proprietary code derived from the dataset, that’s where things get hairy. But the people doing that are responsible for the potential violation, not Huggingface.
On the other hand, totally did not see this particular shit coming. I wonder if we’ll see a rash of “permissive, except LLMs can fuck right off” licenses.
Permissive licences should be the ones to fuck off entirely. GPL or death
No, libraries should remain permissive IMO. Applications can be restrictive if they want to. I just don’t see any point in a copyleft library or framework.
No unfree application should ideally be allowed ever again
You’ll take my code and have a nice life or so help me!
I’ve said it before and I’ll say it again: there is a place for permissive licenses. A great example is reference code for open standards, eg. TCP/IP.
Permissive licences are useful compared to copyleft ones only for unfree actors, which we should fight integrally at every step of the way
Right, I mean I literally published my code openly, so idc lol