3 ms·
> The output of a machine simply does not qualify for copyright protection "Simply"? If it were that simple, surely that would mean that the output of the Unix
by denton-scratch 5y ago
> The output of a machine simply does not qualify for copyright protection
"Simply"? If it were that simple, surely that would mean that the output of the Unix "cp" program would not qualify? What about a DVD copier?
I'm OK with copyright as it used to be, back when I was a teenager; the right expired with the author's life. Corporations couldn't own copyrights. There was no burden on the author to register their rights. And copyright was a civil matter; you sued for actual damages. Infringement wasn't a crime.
I'm not OK with modern copyright law, with criminal penalties, rights that can be transferred to entities that are essentially immortal, and copyright terms that keep getting extended, just before Mickey Mouse and Elvis Presley become public domain.
- tzs 5y ago>> The output of a machine simply does not qualify for copyright protection > "Simply"? If it were that simple, surely that would mean that the output of the Unix "cp" program would not qualify? What about a DVD copier? It means that the output of "cp" does not qualify for copyright protection as a derivative work. The output is still a copy of the input and would be subject to the same copyright as that input. Roughly, a derivative work is a new work that incorporates some copyrightable elements from a previous work. The derivative work gets its own copyright separate from the copyrights of those incorporated elements.
- adriancr 5y ago> Roughly, a derivative work is a new work that incorporates some copyrightable elements from a previous work. By this logic: - someone could go and copy functions and/or entire files from GPL code bases and use them with a different license. - someone could use copilot or similar to learn from all available GPL code. Is resulting code GPL? - someone could use copilot or similar to learn from open source code of their competitors that license doesn't allow them to use. Are the results legal?
- mthoms 5y agoThe definition of a "derivative work" as stated is correct. The copyright status of a derivative work is a separate issue: A derivative work can be considered infringing, and a derivative work can be considered non-infringing (ie. due to Fair Use).
- chalst 5y agoNot necessarily. The object code produced by a compiler might best be regarded as a different form of the source code, even though it is not a copy or a new work, according to http://digital-law-online.info/lpdi1.0/treatise26.html http://digital-law-online.info/lpdi1.0/treatise26.html
- mthoms 5y agoI think they meant “when the output of the machine is significantly original/transformed (i.e. is a new creative work).” I’m not arguing for/against: I just think a straight copy was not what the author intended to be included by that statement.
- b3morales 5y ago> I think they meant “when the output of the machine is significantly original/transformed (i.e. is a new creative work).” No; the author spends some time asserting that the output of a machine is inherently not a creative work: > Machine-generated code is not a derivative work > the argument that the outputs of GitHub Copilot are derivative works of the training data is based on the assumption that a machine can produce works. This assumption is wrong and counterproductive. > This means that machine-generated code like that of GitHub Copilot is not a work under copyright law at all
- mthoms 5y agoThe machine is performing some sort of transformation. Whether you want to call that a "(creative) work" or not is irrelevant to the point I was making: The machine is doing something to the input, and that makes the 'cp' comment I replied to kind of silly. I think we can assume the author doesn't believe that piping bytes through the 'cp' command automatically removes copyright (as the person I replied to suggested).
- CameronNemo 5y agoBut how much of a transformation qualifies as a new work rather than a derivative?