News for hackers. Stuff that matters.
Re:Unity's Open-Source Double Standard: The Ban of VLC by poizan42 on Friday January 12, 2024 @07:33AM (#38967285)
> If you use any 3P library it’s a derived dependency by law. Is that what you are arguing? It’s settled law at this point.

Not it's definitely not. For B to be a derivative work of A it needs to include copyrightable elements of A. But if B merely dynamically links to A then it only contains knowledge of the API surface of A. And SCOTUS refused to rule on the copyrightability of APIs in Google LLC v. Oracle America, Inc. In the EU APIs seems to be explicitly called out as non-copyrightable by Directive 2009/24/EC Article 1(2):

> 2. Protection in accordance with this Directive shall apply to the expression in any form of a computer program. Ideas and principles which underlie any element of a computer program, including those which underlie its interfaces, are not protected by copyright under this Directive.

Re:Unity's Open-Source Double Standard: The Ban of VLC by gumby on Friday January 12, 2024 @09:39AM (#38968491)
An utterly irrelevant side point since the whole question is the use of the implementation not the API.

If you call write() in Microsoft’s libc you must follow Microsoft’s license terms or you don’t have the right to use it. If you call glibc’s write() the same applies. And if you don’t like glibc’s terms you are free to, say, install bsd’s libc or write your own write() implementation (which probably just does a system call anyway).

Re:Unity's Open-Source Double Standard: The Ban of VLC by juped on Friday January 12, 2024 @11:43AM (#38970304)
I don't agree with you but I appreciate you providing me with comments like this to cite when I try to convince people "yes, FSF are really that maximalist; no, that's not a 90s relic they moved on from".
Re:Unity's Open-Source Double Standard: The Ban of VLC by freedomben on Friday January 12, 2024 @01:11PM (#38971675)
> I don't agree with you but I appreciate you providing me with comments like this to cite when I try to convince people "yes, FSF are really that maximalist; no, that's not a 90s relic they moved on from".

unless you make sure that gumby is speaking for the FSF, then that comment does not provide evidence that the FSF believe that. It's merely evidence that gumby does.

I don't understand why people are so quick to take somebody's personal opinion and ascribe it to whatever organization(s) they happen to belong to. This sort of fallacy is why we constantly have to suffer through the "I speak only for myself, not my organization" disclaimers

Re:Unity's Open-Source Double Standard: The Ban of VLC by gumby on Friday January 12, 2024 @02:13PM (#38972530)
> unless you make sure that gumby is speaking for the FSF, then that comment does not provide evidence that the FSF believe that.

And indeed I do not speak for the FSF and never have.

Re:Unity's Open-Source Double Standard: The Ban of VLC by juped on Friday January 12, 2024 @07:25PM (#38976028)
You've caught me in a dastardly logic trap! Now I can never present anyone evidence for the beliefs of the FSF/GPL-user social cluster.

You should try arguing in court for FSF legal theories on linking!

Re:Unity's Open-Source Double Standard: The Ban of VLC by Andrew_nenakhov on Friday January 12, 2024 @02:49PM (#38973025)
And yes, it is a good thing.

Some things shouldn't change just because entitled people are inconvenienced by them.

Re:Unity's Open-Source Double Standard: The Ban of VLC by juped on Friday January 12, 2024 @07:16PM (#38975958)
Really bizarre to bring out the snarl word "entitled" over... the persistence of false legal theories?
Re:Unity's Open-Source Double Standard: The Ban of VLC by chme on Friday January 12, 2024 @01:54PM (#38972275)
> An utterly irrelevant side point since the whole question is the use of the implementation not the API.

I find this interesting, and maybe I am just a bit confused. But here is what I am wondering now.

If it is not about the use of an API but about the use of the implementation, then that would mean that the end-user that is running the application which dynamically links to a proprietary library on the end-users pc the one violating the license terms, not the developer that distributed their code without distributing the proprietary library itself.

And if the developer has the rights to distribute the library, because it is under GPL, then they could do so, and would not violate the license terms, because they are not doing the dynamic linking and using of the implementation, that would happen only when the end-user starts the application.

I never heard about any case against end-users, that for instance used the proprietary Nvidia kernel module, compiled and linked on each end-user's PC.

I don't think that works that way, there has to be more to that than just the usage of the implementation that triggers the license violation.

Re:Unity's Open-Source Double Standard: The Ban of VLC by singpolyma3 on Friday January 12, 2024 @04:17PM (#38974217)
> If it is not about the use of an API but about the use of the implementation, then that would mean that the end-user that is running the application which dynamically links to a proprietary library on the end-users pc the one violating the license terms, not the developer that distributed their code without distributing the proprietary library itself.

yes

> And if the developer has the rights to distribute the library, because it is under GPL, then they could do so, and would not violate the license terms, because they are not doing the dynamic linking and using of the implementation, that would happen only when the end-user starts the application.

If they distribute it together though then it becomes an aggregate work

Re:Unity's Open-Source Double Standard: The Ban of VLC by anthk on Friday January 12, 2024 @09:44AM (#38968560)
No, you are wrong. Libraries have an usage license on linking. Don't comply it, then reimplement your own readline and ship that instead of GNU readline. Period. Motif and Lesstif was an infamous case back in the day. Heck, or using Wine DLL's under Windows instead of the ones bundled from Microsoft.
Re:Unity's Open-Source Double Standard: The Ban of VLC by poizan42 on Friday January 12, 2024 @10:05AM (#38968848)
A third party library can claim whatever it wants in its license, that doesn't make it enforceable. There needs to be some mechanism that causes the terms of the license to apply to you. If you don't distribute any copyrightable parts of a third party library then you (may?) not be under any obligation to adhere to its license.
Re:Unity's Open-Source Double Standard: The Ban of VLC by armada651 on Friday January 12, 2024 @11:42AM (#38970292)
Even if you don't personally violate the license, the license may still be enforceable against the users of your program. When the user executes your program and it loads other libraries into its memory space, then it definitely has become a derivative work and the terms of the libraries will apply to the program as a whole.
Re:Unity's Open-Source Double Standard: The Ban of VLC by simiones on Friday January 12, 2024 @12:59PM (#38971505)
At least in the USA, the copying of a program you legally received into working memory doesn't require a license of any kind, it is a type of fair use. I believe the EU has an explicit exception to copyright for the same reason. So I don't think any problem would arise when running the programs.

The only pertinent question is whether a program B designed to require library A is a derived work of library A or not - and this is a question for the copyright courts, the license of library A has nothing to say about this.

Now, I think even if it were established that program B is not a derived work of library A, it could be possible for library A to have a license that says "you're not allowed to distribute this library to others unless both you and they agree to never link program B or works derived from it with library A". The GPL could be modified to say something like this, and it may still match its original goals - though it may be more difficult to litigate this type of license term (in many countries, license or contract terms can be declared too onerous and be ignored).

Re:Unity's Open-Source Double Standard: The Ban of VLC by pests on Friday January 12, 2024 @05:02PM (#38974727)
> I think even if it were established that program B is not a derived work of library A

I don't think it ever will be.

> program B designed to require library A

How do you design program B to require A, without inspiration from A?

I believe you can't. For a silly example, take a puzzle peice. To integrate support for your puzzle in my work, I'm gonna have to copy some of your edges.

Re:Unity's Open-Source Double Standard: The Ban of VLC by armada651 on Friday January 12, 2024 @05:05PM (#38974759)
> At least in the USA, the copying of a program you legally received into working memory doesn't require a license of any kind, it is a type of fair use. I believe the EU has an explicit exception to copyright for the same reason. So I don't think any problem would arise when running the programs.

My point wasn't about copying into memory being a license violation, rather the fact that you're combining two works together into a single program that violates the license of one of the works. Who is liable for the violation in that case? The user who combined the works together or the developer who created a program that instructs the user to combine those works together?

Perhaps you're selling a book that's derivative of Stephen King's novels, but instead of actually including text from his novels you insert pages that just say "insert chapter 5 from the Shawshank Redemption here". Even though it contains instructions to create a derivative work, it is not in itself a derivative work.

However if the reader follows those instructions and creates a completed work by inserting those chapters as instructed. That completed work definitely is a derivative work of Stephen King's novels.

Re:Unity's Open-Source Double Standard: The Ban of VLC by tzs on Saturday January 13, 2024 @01:37AM (#38977825)
In the case of computer programs, but not Stephen King novels, in the US there is 17 USC 117 to consider which includes this:

> (a) Making of Additional Copy or Adaptation by Owner of Copy.—Notwithstanding the provisions of section 106, it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program provided:

> (1)that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner, or

> (2)that such new copy or adaptation is for archival purposes only and that all archival copies are destroyed in the event that continued possession of the computer program should cease to be rightful.

That should cover most likely scenarios of someone combining programs and/or libraries from various sources on their own computer as long as they own the particular copies of those programs and/or libraries that they are combining.

Re:Unity's Open-Source Double Standard: The Ban of VLC by p91paul on Saturday January 13, 2024 @05:25AM (#38978673)
I don't think the user can be held liable under the GPL. The GPL says:

> This License explicitly affirms your unlimited permission to run the unmodified Program

> You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force

So the GPL restrictions apply only on redistribution to others. You can do whatever you want on your systems.

Re:Unity's Open-Source Double Standard: The Ban of VLC by simiones on Monday January 15, 2024 @03:36AM (#38998607)
As a general rule, anything you do with a copyrighted work in private quite possibly falls under fair use, as long as the copies you are using were obtained legally. If you want to write Shawshank Redemption fan-fiction and read it to your kids in bed, even if Stephen King found out and decided to sue you, you're probably covered under fair use. Creating a program just for yourself that uses two separate copyrighted programs (that you obtained legally!) is almost certainly legal - even if it would be completely illegal to distribute that program to others.

This gets murkier if you're using it in a commercial setting, though.

Re:Unity's Open-Source Double Standard: The Ban of VLC by anticensor on Saturday January 13, 2024 @06:49AM (#38979137)
Onerousness defence can be defeated by anti-severability clauses, if that clause is written to require full reversal of performance in case of termination.