this post was submitted on 14 May 2026
398 points (99.5% liked)
Technology
84643 readers
3841 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Your thinking is off, the GPL and derived licenses like the AGPL are viral on purpose. They apply to everybody who uses, downloads, or accesses the software (in the case of the AGPL) and they are explicit about this:
what i'm reading from that is that both parties must agree that the work has been conveyed. with the risk of going all sovcit, if the conveyed item is a binary, and the producer does not send the source code to the consumer as instructed by the license, can the consumer really pull the source and distribute it? surely if the license is broken the work falls back on default pecmissiots, e.g. all rights reserved?
In the general case, the person or persons who distributed the binary would then have done so illegally. In order to distribute, you have to follow the terms of the license. So them attempting to go after anyone downstream of them at that point is sort of like calling the police because someone stole your drug stash. And if there's an upstream beyond the illegal distributors, they're practically waving a "Sue me now!" placard in their direction.
The originator of the code, above whom there is no upstream, is allowed to offer it under more than one license (including a mixture of free and closed licenses), but the specific license in force has to be specified with each distributed copy.
Do you have an example of a project that has both free and commercial licenses? How does that work in practice?
The first one that comes to mind is Qt (the widget toolkit). While I'm not sure the current owners still do this, Trolltech offered the earlier versions under both the GPL and a commercial license that I think included paid support. I assume any sales under the commercial license were to companies who wanted to include it in their closed-source software.
Maybe read the GPL ;)
But the language defines that if you distribute a binary, you must make the source available, and that source is allowed to be taken, modified, redistributed as binary and source, as long as the person doing the modifications attributes you and all other previous authors.
It doesn’t matter if that binary comes as a firmware on a device the user purchased.
The distributor does not have to distribute the source with the binary, they just have to make it available, for free, and they cannot stop anyone using it as defined above.
Breaking the license does not change how the software is licensed, it just puts the entity doing the violations in violation of a license.