News for hackers. Stuff that matters.
Re:Unity's Open-Source Double Standard: The Ban of VLC by hedora on Friday January 12, 2024 @09:58AM (#38968753)
Are these new changes with LGPL 2.1? I don’t remember it containing the modification and relinking restrictions in the past. It kind of defeats the purpose of the LGPL IMO.

As an aside, it really bugs me that the GPL morphed into this thing that gives developers the freedom to run privacy violating and user-abusing cloud services, but doesn’t allow manufacturers to ship the same stuff on physical (and perhaps offline) hardware the end users have physical control over.

When the GPL 3 added the anti-TiVo clause, it really should have also added AGPL’s anti-google clauses at the same time.

Anyway, I guess the above restriction means I won’t be using LGPL for stuff I write at work, even though most of what we do gets open sourced anyway.

Re:Unity's Open-Source Double Standard: The Ban of VLC by kmeisthax on Friday January 12, 2024 @11:06AM (#38969716)
> When the GPL 3 added the anti-TiVo clause, it really should have also added AGPL’s anti-google clauses at the same time.

They tried that, everyone balked. You know how Linus Torvalds rejected GPLv3 for Linux specifically because anti-TiVo[0] would be "changing the deal"? Imagine that times a thousand.

Furthermore, AGPL is only an anti-Google license specifically because Google is as internally afraid of it as Microsoft is of GPL. You can defeat the Affero clause by putting the software behind a proxy, for example. Furthermore, the Affero clause is only appropriate for web applications - ideally ones in dynamic languages that execute from source that remains on disk. Slapping it on all GPL software would be really, really dangerous. I've heard of people using AGPL on Ethernet PHYs - how the fuck do you offer source code to every packet that crosses an Ethernet switch?

If you really want a license clause that would absolutely decimate any corporate freeloading behavior, you want OpenWatcom's anti-private-forks clause[1]. It does everything AGPL tries to do, with fewer legal loopholes. But good luck getting that past RMS. The problem with supra-GPL copylefts is that anything that is legally watertight to a corporation is also going to impinge on a lot of freedoms we enjoy. Remember: the whole point of the GPL is to reject copyright, and that specifically means lots of corporate freeloading, because the whole point of copyright is to stop corporate freeloading.

[0] From what I've heard, the anti-TiVo clause in GPLv3 is actually less strict than the FSF advertised, at least relative to how TiVo used Linux. I can't find the original article I heard this in, though!

[1] Specifically, the OpenWatcom license requires distribution of source code whenever you use a modified version of the software.

Re:Unity's Open-Source Double Standard: The Ban of VLC by freedomben on Friday January 12, 2024 @12:46PM (#38971335)
I mostly agree with you, with one exception:

> Remember: the whole point of the GPL is to reject copyright, and that specifically means lots of corporate freeloading, because the whole point of copyright is to stop corporate freeloading

I don't think this is true. My understanding (which could be flawed) is that the whole point of the GPL is to weaponize copyright in order to guarantee freedoms, not to reject it (a subtle but important distinction).

Also the whole point of copyright doesn't seem to be to stop corporate freeloading, though that is of course part of it. It's point is to ensure that the original creator has rights to benefit from the work, whether that means getting stolen from by a huge corporation or stolen from by teenagers passing memes over the internet, or adapted by an individual/sole proprietor as part of some larger work, etc. My guess is we probably agree on this part and the debate is probably over semantics (i.e. you might have meant "business in general" by "corporate" rather than specific corporations).

Re:Unity's Open-Source Double Standard: The Ban of VLC by dcow on Saturday January 13, 2024 @01:12AM (#38977738)
RMS famously refers to the GPL as a hack on the copyright system. It comes from an axiomatic belief that restricting copying in the computer age is fraught. To put yourself in the headspace, imagine the ivory tower discussion: look at how stupid this law is… don’t the plebeians know that computers copy data around the system and the network all the time to even function, literally digital would be dead if we actually enforced the letter of copyright law, oh and data is context dependent anyway so the same underlying data could manifest two wildly different concepts so you have to bind data and context not just allow people to claim rights to arbitrary strings of bits etc. etc. So it follows that copyright is harmful because if enforced it would dismantle cyberspace. The hack is to use copyright law to enforce licenses that perpetually reject copyright to make sure users have custody of their hardware and can’t be inhibited from freely running whatever combination of instructions they can dream up. A better reality would be something more akin to the world running arch linux and compiling every software from source (but we can’t have that because evil wealth extracting corporate automatons will steal your source, license it and sue you, hence copyleft). And since chefs can’t copyright recipes programmers shant copyright programs, which are just instructions that tell your machine how to achieve some outcome. You are free to sell the best tasting implementations of your programs as packaged SaaS software, though. Your value as a software chef is in the quality of the meals you serve not the knowledge of the specific ingredients used to create them.
Re:Unity's Open-Source Double Standard: The Ban of VLC by dingnuts on Friday January 12, 2024 @01:51PM (#38972227)
>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Re:Unity's Open-Source Double Standard: The Ban of VLC by bombcar on Friday January 12, 2024 @02:53PM (#38973083)
It's never been tested in court, but the theory is you with company A run an Affero GPL (modified code) server. It's not accessible to anyone outside company A, except me, with a proxy-ish server in Company B (which may or may not be controlled/related).

Then I'm the only user of your software, and never request the code, even though ten billion users use it via my proxy.

Re:Unity's Open-Source Double Standard: The Ban of VLC by singpolyma3 on Friday January 12, 2024 @04:04PM (#38974041)
This is only gonna work with a very specific corporate structure, if it even works at all. Judges don't tend to fall for this kind of "being cute"
Re:Unity's Open-Source Double Standard: The Ban of VLC by TylerE on Friday January 12, 2024 @04:46PM (#38974572)
I'm not so sure it's just being cute. Define a bright line difference between this API proxy and something like an IRC server. Fundamentally it's an RPC black box. Client sends a command and gets a response. How that response is generated the client has no way of knowing or differentiating. For the defense to fail, wouldn't you have to prove that end user C was a recipient of software from company A? How could this possibly be true when user C cannot observe even the existence of A?

Like, imagine this hypothetical.

Set up a server. For each unique client that exists, it proxies to one of two backends. One is wrapping an LGPL library. The other is wrapping a cleanroom non-CL implementation.

A given user will always get one or the other. Think of it as being assigned off the high bit of a user hash or something.

Which users have rights under the LGPL? Remember that half of them have never used the (wrapped) LGPL implementation, and NONE of them can tell which group they are in.

I don't actually see the difference as being that distinct from the long accepted fact that a program compiled by a copyleft compiler or running in a copyleft interpreter is not itself inherently copyleft.

Re:Unity's Open-Source Double Standard: The Ban of VLC by kmeisthax on Friday January 12, 2024 @04:36PM (#38974458)
The idea is that the proxy removes all the AGPL compliance features from the web application. So if your app has a View Source link that spits out all the *.php files on disk, your proxy blocks that link. AGPL prohibits you from removing parts of a program intended to implement a "View Source" link, but it doesn't put any specific limitations on the conduct of other, unrelated programs.

The only other thing I could think of to prevent this would be a DMCA 1201 claim - i.e. that the view source link is a DRM system, and that a proxy that removes those links is illegal. Except all v3 licenses explicitly foreclose the ability to make DMCA 1201 claims relating to features of the software.

My guess is, Mastodon used AGPLv3 primarily because the Affero clause scares off big tech companies, notably Google. I don't have access to any IRC logs or issue tracker comments to prove this is the case, though.

Re:Unity's Open-Source Double Standard: The Ban of VLC by zerocrates on Friday January 12, 2024 @05:16PM (#38974872)
There's much that's untested about these licenses in practical terms. This scheme of producing the source but also blocking it... it's hard to see it standing up in court.

Let's assume you modify the AGPL program, so the remote interaction clause kicks in. If you have the software provide links to the source, but you yourself also strip those out before any of those remote-interacting users can ever see or use them, I don't think a court would have a problem saying that you're not actually "offering an opportunity" for the users to download the source and are therefore in violation.

Re:Unity's Open-Source Double Standard: The Ban of VLC by everforward on Saturday January 13, 2024 @04:15AM (#38978349)
Quoting from the AGPL:

"To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying."

"You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:"

I think you would have a very, very hard time arguing that you had conveyed the source under this definition.

This is like paying a parking ticket on a credit card, charging it back, and then arguing that it's paid because you sent the money.

Re:Unity's Open-Source Double Standard: The Ban of VLC by not_the_fda on Friday January 12, 2024 @02:52PM (#38973055)
[0] The anti-TiVo clause only applies to "User Product" defined in the GPL as a consumer device, i.e. not a device you sell to a business. The idea being business's can fend for themselves. Its perfectly valid to create say a medical device that is sold to hospitals and have it locked down and use LGPL code. The hospital actually wants it locked down.
Re:Unity's Open-Source Double Standard: The Ban of VLC by singpolyma3 on Friday January 12, 2024 @04:02PM (#38974019)
Re:Unity's Open-Source Double Standard: The Ban of VLC by kmeisthax on Friday January 12, 2024 @04:33PM (#38974420)
> [so], these words in GPLv3: “The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.” mean that the proprietary software that is not a combined work with the GPLv3'd work must also function?

> Absolutely. And I wrote it specifically to do that!

Welp, looks like I was wrong about that one.

Re:Unity's Open-Source Double Standard: The Ban of VLC by mort96 on Friday January 12, 2024 @10:07AM (#38968876)
Huh? The whole point of the LGPL is to say, "you can use the LGPL'd code in your closed-source product, but the user must be able to replace the LGPL part of your product with their own version". The way to achieve that is to either use some kind of dynamic linking where the user can provide their own .so/.dll/.dylib of the LGPL'd library, or to provide the object files so that the user can statically re-link the application with their own version of the LGPL'd library.

This is different from GPL, since you can't use GPL'd code in your closed-source product at all, not even if you let the user replace the GPL'd portion with their own version.

What purpose of the LGPL is defeated?

Re:Unity's Open-Source Double Standard: The Ban of VLC by gorkish on Friday January 12, 2024 @11:24AM (#38969977)
> What purpose of the LGPL is defeated?

The purpose of /which/ LGPL? And that's the thing. After GPL demonstrated that it had teeth and got some case law underneath it, the "family" of derivatives exploded, each one of them identifying as "open source" but each with their own additions, removals, modifications or other opinions on what "freedoms" they convey (mostly removals).

There are those of us out here who believe that the core purpose of all of these licenses were defeated a long time ago when all of this legal swizzling first began. I personally hate GPLv3, AGPL, LGPLv3, etc. with a fiery burning passion; thank god we were able to see some transformative projects emerge under actually free licenses before everything got ruined.

Re:Unity's Open-Source Double Standard: The Ban of VLC by mort96 on Friday January 12, 2024 @12:18PM (#38970880)
> The purpose of /which/ LGPL

Either 2.1 or 3.0 I guess, the difference between the versions isn't that relevant to hedora's question.

The GPL exists to protect users against companies which develop proprietary software. If you prioritize the freedom of companies to restrict users over the freedom of those users, it makes sense that you'd dislike the GPL style licenses.

Re:Unity's Open-Source Double Standard: The Ban of VLC by freedomben on Friday January 12, 2024 @12:49PM (#38971380)
> I personally hate GPLv3, AGPL, LGPLv3, etc. with a fiery burning passion; thank god we were able to see some transformative projects emerge under actually free licenses before everything got ruined.

Why do you hate them so much? Is it strictly as a developer, or as a user?

As a developer I've certainly felt constrained and annoyed by them at times, and I'm very glad there are alternative open source licenses available, but as a user I can't imagine a scenario where you would hate them. After all, the freedom they guarantee is to the user, not the developer.

Even as a developer though, the family has it's place. I don't think Linux would be a thing had it had a more "permissive" license. That GPL is what forces the big corps to contribute their improvements back. If not for the GPL, I think it would be in a position similar to that of BSD, and the majority of users would have no choice but to use a proprietary OS

Re:Unity's Open-Source Double Standard: The Ban of VLC by bombcar on Friday January 12, 2024 @02:55PM (#38973107)
Notice the lack of "GPL" in that list, and I'm partially in agreement.

The GPL is amazing and wonderful, but the various "attachments" of the GPL are more weaponized (and to the detriment of users!) than the GPL ever was.

I'm glad the kernel stuck with GPLv2, and I wish other things had, too. A GPLv3 Linux Kernel would likely have helped a BSD tremendously, though but I think having everyone work on the same kernel without reservations has been an unmitigated good.

Re:Unity's Open-Source Double Standard: The Ban of VLC by singpolyma3 on Friday January 12, 2024 @04:07PM (#38974078)
GPLv3 isn't enough different from GPLv2 to matter in practice, usually. It's mostly clarifications like the cure provision.
Re:Unity's Open-Source Double Standard: The Ban of VLC by jlokier on Friday January 12, 2024 @05:01PM (#38974715)
It's different enough that Apple thinks it's only safe for them to ship GPLv2 software on MacOS devices, not GPLv3.

This might have something to do with the way they sign shipped versions and use TPM security to verify what's run, even though you can manually disable some of this if you want.

So all GPL the software shipped on MacOS devices is stuck at the last version which used GPLv2, and they rewrote Samba which they had previously shipped, whose last GPLv2 version is too out of date to keep using.

Re:Unity's Open-Source Double Standard: The Ban of VLC by mort96 on Friday January 12, 2024 @05:32PM (#38975058)
Wait are you only angry at the AGPL? Or what are you calling attachments to the GPL?

LGPL is a relaxation of the GPL, by the way.

Re:Unity's Open-Source Double Standard: The Ban of VLC by hedora on Friday January 12, 2024 @10:18AM (#38969036)
I thought the purpose of the LGPL was that it could be used for libraries without tainting the stuff the library is linked against with viral GPL restrictions.

Concretely, using gcc with default settings will bring in glibc and compiler intrinsic code snippets which were both LGPL last time I checked. If I use GCC to compile and statically link closed source code that I have a redistribution without modification license for, then I can’t redistribute my binary without violating my license for the closed source code.

Ouch! MUSL + clang it is, I guess. (I value my users’ right to own and operate computers even higher than their right to recompile code, so I’d rather not restrict my lgpl tainted binaries so they can only run in the cloud).

Re:Unity's Open-Source Double Standard: The Ban of VLC by rescbr on Friday January 12, 2024 @12:07PM (#38970719)
IIRC, GCC specifically uses GPL + runtime license exception to avoid this scenario
Re:Unity's Open-Source Double Standard: The Ban of VLC by mort96 on Friday January 12, 2024 @12:14PM (#38970817)
glibc's LGPL is generally no problem because you honor that simply by dynamically linking against it. Normal desktop Linux distributions do have a "suitable shared library mechanism" as the LGPL calls it, so if your binary is dynamically linked against glibc, your users are free to link against the user's modified libc. The "Distribute object files to allow re-linking" thing only becomes relevant if you don't use a "suitable shared library mechanism" to dynamcially link against the LGPL-licensed library.

However, if you do choose to statically link against glibc (which is highly discouraged, for technical reasons) then yeah, you have to give your users access to object files or some other mechanism to statically link against a different version of glibc than the one in the executables you ship. And yeah, this might potentially be incompatible with the licenses for certain proprietary libraries, which simply means that you can't statically link against those binaries and LGPL-licensed libraries at the same time.

The stuff in GCC which gets includes into your binary (such as crt0.o, and whatever code it generates) is except from the GPL.

I have no idea what you're talking about wrt restricting your users to only run your binaries in the cloud.

Re:Unity's Open-Source Double Standard: The Ban of VLC by hedora on Friday January 12, 2024 @12:40PM (#38971242)
If you sell a device with Linux and a proprietary blob on it, then you’re arguably doing the linking, not the user. On top of that, if you enable link time optimization, then you have to link at build.

All of this would be allowed if you put the same device in a data center, and then had the user connect to it remotely.

Re:Unity's Open-Source Double Standard: The Ban of VLC by mort96 on Sunday January 14, 2024 @06:21AM (#38989469)
Yeah, the embedded Linux context is messy. I don't know how the rules play out there (and I would be surprised if anyone truly knows). I thought we were talking about the general computing device use case.

Link-time optimization isn't really relevant from what I understand; it's about optimizing across different object files when linking them together, it shouldn't have any impact on dynamic linking.