I'm not the author of this project, but in my understanding, it's the same as if you were to write the code yourself. The project doesn't publish anything and it works entirely locally aside from LLM calls (which could in the future be 100% local as well). So you remain the author and have complete control over the license of the generated code.
If I run an OCR software 100% locally, do I get the copyright on the scanned result of Harry Potter?
Don't understand: using a giant LLM locally negates all the copyrights contained in the LLM? In which country is that a law?
So not entirely locally. Yes these could eventually also run locally but OP’s point still stands.
If it runs 100% locally then yes, it would be safe to use.
openai's official stance is that it will never use API calls as training data, and that in my understanding it may retain API call data for up to 30 days for compliance purposes, but that it legally won't store it beyond that (whereas chatgpt convos are meant to be stored and used for training purposes).
as a next step, they could provide a swappable version of the LLM provider using something like https://github.com/imartinez/privateGPT, https://github.com/alexanderatallah/window.ai, etc. would love to have a standard develop here as the community matures around LLM usage
The license is the one of the original, since this is unambiguously a derivative work.
I find this reasoning a bit flimsy. Copyright doesn't have anything to do with publishing, and is it really that clear that you are the sole author of the derived work?
Creators need to use restrictive licenses, then all of these parasitical corporations will cease to exist.
I can't talk about licensing for content creators (like youtube), because I do not have much experience about it.
- the copyright status of the output of LLMs is ambiguous
- this ambiguity represents a legal risk to the users of LLMs
- given that ambiguity, nobody should use LLMs for work that is intended to be copyrighted
It’s not clear to me if any of these are true individually, never mind all together.
Maybe the copyright status is ambiguous but I think the probability that the output of LLMs is owned by anyone other than API caller is very low. You can copyright works, but you can’t copyright the ideas within those works.
Possibly this represents a liability issue but I think the probability of that is vanishingly small. Just because a legal theory exists doesn’t mean it’s going to be enforceable - one of the reasons for the existence of Uber, youtube, etc. if it’s a fait-accompli it’s not a risk.
Finally, it representing a risk of copyright liability is still just a business decision. I would guess that existing software projects are riddled with code snippets of ambiguous or incompatible licenses. All it takes is one person to copy a function that is GPL and label it otherwise and then it’s out in the world, technically running amok. It is probable that under the strictest definitions, every software company is engaging in some low level of copyright infringement. All-in, this means that while it’s a risk, it’s a risk you’re probably already taking and so you might reasonably conclude to ignore.
Any lawyer will tell you if the first two points are unclear the third point is rock solid - don't use tools that have ambiguous copyright terms until AFTER the big legal fallout/legislation unless you are willing to bet the entire farm.
If the law is so unclear that lawyers can't determine legality and are waiting for additional guidance from the lawmakers, shouldn't it be legal by default?
A law like this seems pretty much impossible to enforce, though. Even if it turns out that GPT is just parroting remixes of GPL code, all examples of generated code I've seen are fully indistinguishable from code someone may have come up on their own - with the exception of contrived cases where someone is actively trying to get it to output a particular fragment of code verbatim.
My common sense says that without a tiny bit of doubt, copilot is utterly outlaw so far, essentially stealing gpl code where the only price was credit. It probably has several other problems but that is one that anyone can see. I don't mean everyone agrees, I mean the information needed to make the judgement is all present to all observers without needing to see the code or the training process or be a lawyer. There are countless examples of regurgitated gpl code, with no credit. End of search.
It's inexcusable because it would have been almost zero burden to get everyone's consent to be included in a collective credit. They didn't even do that.
So, whether or not this assertion of mine ever amounts to anything, it's a simple example of something being illegal all along, but maybe you don't know it until after you do it, and it gets examined and judged, and the judgement goes the way that burns you.
It doesn't require any new law.
If you disagree, how many users are on your twitter clone right now? Exactly.
Don’t trust OpenAI? Use Microsoft.
Don’t trust Microsoft? Run TII Falcon locally.
No one was asking those questions when the backbone of any modern tech company was, ironically, thousands of copy/pasted lines of code from StackOverflow and any other references that come up in a Google search. The number of SDE’s I know who can write code without a web browser is vanishingly small.
I’m sure these question can be easily answered by looking it up, so why would LLMs be any different? You have control over what the LLM generates (prompts).
Never seen it questioned that Windsor & Newton could actually be the copyright holder for half the world's art.
If I open up Photoshop and make a new file, I own my art. So why would me opening up an existing PSD and moving all the pieces around and then claiming it as my own be an issue?
I don’t think anyone would question this at all if the model were trained only on your own data. It’s the part where a bunch of other people’s stuff was involved that makes it fuzzy enough to be an open legal question.
I can sort of see that but a) I'm also seeing it posited that the copyright could belong to either ht model or the company that produced the model (where does that logic come from?) and b) My own creativity is trained on the works of many others but my work is still my own, why is this different for an LLM?
I think a same result though is that any work translated by the original author counts as a translation that maintains but doesn’t extend copyright.
Consider a hypothetical LLM that was trained on data having a single undisputed copywrite owner. What would be the legal status of it's output?
In that case the tool would almost certainly generate a derivative work, which would be a copyright violation. It's the same as if I took sick strong inspiration from a certain song that I wrote a new one with the same melody and chords, which has happened a bunch of times.
But generally LLMs are most useful when they're trained on a broad enough corpus to avoid these issues.
Anyway, now consider an LLM that was trained on two corpuses(?) with two distinct undisputed owners.
The question is more like this, if google books has an api that lets you retrieve one sentence from any book, and you use it to fetch whole chapters of valuable books written by actual insightful authors.
Do you really deserve to claim to have written the book you patch together from that? Especially, do you really deserve to not only benefit from selling the new book, but not even acknowledge nor pay a percentage to the original authors?
When you write a program using a library, there is no such ambiguity or credit-washing. You wrote your app, the library authors wrote the library.
copilot is essentially stripping that. You get to not only write your app, but look like, and even, apparently, feel like, you produced everything that went into it. All that stuff that was done by someone else and gifted to you, well that's all just the tools you the real artist used. It's absurd to credit a paint brush eh?
I don't know which forums you are discussing these things in, but this is the first comment on all discussions about AI on HN.
1. Author
2. Copyright holder
3. Copyright license
...of the code generated by this tool?
Unless the answer to all of these is unambiguously "the original", then you shouldn't be using such tool on any code, especially on your employer's intelectual property.
Sorry to be so negative about it but this is something that I see skipped over in all discussions related to AI. Just because it's AI does not make it immune to copyright law. You're giving away your code to a 3rd party company under their terms and conditions, and receivig some new code back, again under their terms and conditions. The fact that it uses AI under the hood is irrelevant, you're dealing with a business that produces you an output and you should know the terms before submitting anything to them, especially if you don't own that thing.