7 ms·
The falsehoods of anti-AGPL propaganda (2020)
- Proven 5y ago> That’s pretty easy, right? I’m positive that your business has to deal with much more onerous contracts than the AGPL. You're missing the point. They aren't choosing between the AGPL and Oracle's EULA. They're choosing between the AGPL and other open source software licenses. First, every time some AGPL code has to change, a business has to review the amount of work that will go to it (patch or rewrite and replace), review the patch including legal review, etc. Secondy, this requirement resticts my freedom. If the same code is licensed under a permissive license, I wouldn't have to do anything. Once it's approved for internal use, the overhead of dealing with OSS is almost gone. Regardless of Google's falsehoods, it's undeniable that a permissive license doesn't restrict my freedom. And that's it - I don't need more anti-AGPL propaganda to avoid its use. If I can use the MIT or Apache or BSD licensed code, I will. Even if it's slightly worse, I'll pick it over AGPL-licensed code because in the mid and long term it won't cost me as much. > Google wants to be able to incorporate FOSS software into their products and sell it to users without the obligation to release their derivative works. Who doesn't? Why should anyone bother furthering your AGPL agenda over own interests and the freedom offered by permissive open source licenses? I can't believe this crap topic comes up every so often.
- hdjjhhvvhga 5y agoI think you're both right. AGPL is worse for any SaaS business if you plan to build it around your modifications of that software, period. That's very simple and I think nobody disagrees with it. However, there are many cases where AGPL is the best solution. That is, when you plan to release an original piece of software, not just modify someone elses's project, and you specifically want to prevent companies like Amazon or Google to profit from it without giving you anything back. In this case, dual AGPL + commercial licensing is a good way to go. People need to know this instead of blindly copying "Google says AGPL is bad so we must avoid it at all costs."
- t-writescode 5y agoHow often do people do AGPL + commercial licensing, I wonder?
- nabla9 5y agohttps://en.wikipedia.org/wiki/List_of_software_under_the_GNU_AGPL https://en.wikipedia.org/wiki/List_of_software_under_the_GNU...
- t-writescode 5y agoWhat about ones with AGPL *and* commercial licensing?
- tzs 5y ago> However, there are many cases where AGPL is the best solution. That is, when you plan to release an original piece of software, not just modify someone elses's project, and you specifically want to prevent companies like Amazon or Google to profit from it without giving you anything back. In this case, dual AGPL + commercial licensing is a good way to go. That might work if all you care about is making sure Amazon publishes their modifications to your software. The most common complaint though is Amazon offering support for the software, thereby removing the need for those who use the software on Amazon to purchase support from the original developer. Making your software AGPL doesn't help at all with that. If Amazon offers support for your software on their platform, they can kill your support revenue even if they make no modifications whatsoever to your software.
- hdjjhhvvhga 5y agoBut this is not related to licensing: anyone can offers support for any piece of software and, as far as I can tell, there is no way to prevent that in a license. Otherwise Oracle would have eliminated Rimini Street years ago (the only thing they got is $90M in the recent lawsuit which is almost nothing).
- goodpoint 5y ago> every time some AGPL code has to change, a business has to review the amount of work that will go to it (patch or rewrite and replace), review the patch including legal review This is plain false. AGPL code can be worked on just like any other license or your own proprietary product. > Secondy, this requirement resticts my freedom This is like being prohibited to kidnap other people. We are not allowed to do it because it would restrict other's people freedom down the line. Another example is the https://en.wikipedia.org/wiki/Paradox_of_tolerance https://en.wikipedia.org/wiki/Paradox_of_tolerance As a society, we cannot have the freedom to access and modify code together with the freedom to lock down and proprietize code. They are in conflict. > it's undeniable that a permissive license doesn't restrict my freedom It is provably restricting mine. My android phone and many other devices are full of proprietary stuff that I cannot access, review and trust, despite being built with large amounts of FOSS. Because the licensing allowed taking away freedom from the end user.
- rakoo 5y ago> Secondy, this requirement resticts my freedom Your freedom as a middle-man is not important. What matters for GNU licenses is the freedom of the final user. > Who doesn't? Why should anyone bother furthering your AGPL agenda over own interests and the freedom offered by permissive open source licenses? > I can't believe this crap topic comes up every so often. You don't care about user's freedom but only yours, other people feel the opposite. There is ample space for a discussion on both viewpoints.
- RcouF1uZ4gsC 5y ago> Obligatory: I’m not a lawyer; this is for informational purposes only. The issue with the AGPL is that you really need to be a lawyer to understand the nuances. What constitutes a “derived work”. What is the precedent for what is a “derived work”? With MIT, BSD, you put in the attribution and call it a day.
- varajelle 5y ago> With MIT, BSD, you put in the attribution and call it a day. Where exactly and how do you need to put the attribution? You still need to be a lawyer to be able to answer this question. Meanwhile many project just copy paste MIT and BSD code and just "forget" the attribution.
- Klasiaster 5y agoAgree with the ignorance for attribution demands. Apache 2.0 is also everywhere yet nobody takes it seriously (it demands a lot!) and just treats it like the 1-clause BSD license.
- pabs3 5y agoWhen I have reported MIT/BSD license violations, the copyright holders have just said they don't care.
- haukem 5y agoFrom my experience most commercial software licenses are much harder to understand. Especially if you want to redistribute commercial software and do not want to pay for it, it gets very complicated.
- bawolff 5y agoThe thing that's really unclear to me about the agpl: - where is the line between "config" and "program". If i take the license literally, why wouldn't my db password be considered part of the derrived work? More generally, many programs have actual code as config. Where is the line? - security issues - if there is a security issue and it has an emergency patch but there is some coordinated disclosure going on so its not public yet, is this an agpl violation? -antispam meassures - antispam stuff tends to benefit from security through obscurity. Can i embed antispam checks directly in the agpl source without revealing.
- southerntofu 5y ago> If i take the license literally, why wouldn't my db password be considered part of the derrived work? Configuration is just a short artifact. It's not a creative work and is therefore not copyrightable at all, whether by AGPL or otherwise. > if there is a security issue and it has an emergency patch but there is some coordinated disclosure going on so its not public yet, is this an agpl violation? No because: - if you are coordinating with the developers, then you have their explicit permission to temporarily withhold those changes (AGPL copyright holders can still grant exceptions to the license) - AGPL does not mean you must provide up-to-date source code in an automated matter; you have to be able to provide the source code upon request, and there's nothing in the license preventing any forms of delays (much less so for ensuring security of users) > antispam stuff tends to benefit from security through obscurity. Can i embed antispam checks directly in the agpl source without revealing I'm not convinced obscurity helps against spam at all. DKIM and blocklists have done much more against email spam than any form of "security by obscurity" corporate scheme has. However, if the logic is separate from the configuration, you would have to publish the edited source code (the logic), but could retain the actual configuration (because once again, configuration is not copyrightable).
- cylinder714 5y ago>AGPL does not mean you must provide up-to-date source code in an automated matter; you have to be able to provide the source code upon request, and there's nothing in the license preventing any forms of delays (much less so for ensuring security of users) I think it does, if you modify the code. From section 13 of the AGPL: "Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software."
- Hamuko 5y agoThis post makes it seem like only big bad megacorps like Google (and people drinking their kool-aid) would have an issue with AGPL, even though you can definitely find individuals who object to it as well. marcan for example has been vocally against AGPL on multiple occasions. https://github.com/mastodon/mastodon/issues/49#issuecomment-294299918 https://github.com/mastodon/mastodon/issues/49#issuecomment-... https://twitter.com/marcan42/status/1384834585834319875 https://twitter.com/marcan42/status/1384834585834319875
- cercatrova 5y agoHonestly, I initially wanted to make my software AGPL because it seemed quite attractive, but all these problems, or supposed problems even, just made me not want to deal with it and I made the software proprietary instead. It was a SaaS that I was fine with letting end users copy and tinker with but didn't necessarily want big companies to do the same. Now that's obviously against Free Software, but I couldn't be arsed to deal with the nuances, and I found that at least for a SaaS that you'd like to make money off of, proprietary is the likely way to go.
- swiley 5y agoBig companies don’t touch AGPL stuff with a ten foot pole.
- ttiurani 5y agoThis is good to know and precisely the reason I use AGPLv3 whenever I can. IMO open source developers writing code on their free time for the common good or just for fun should make sure with a licence like AGPLv3 that their work isn't appropriated by fundamentally immoral corps to increase profits. It isn't a badge of honor that a FAANG uses your library, it's just exploitation.
- LinuxBender 5y agoI witnessed this. There was a process to submit licenses to legal. People didn't follow the process and their projects were killed off just prior to completion as audits would surface licenses. This happened multiple times. People tried to argue with legal, but they wouldn't even entertain the conversation.
- pabs3 5y agoIts not exactly hard to comply with the AGPL. Just choose either to not modify the software, or if you do then link to the git repo you store the changes in.
- swiley 5y agoIt doesn't matter though. The GPL was easy to comply with, AGPL completely freaks them out.
- jasode 5y agoThe HN "past" link doesn't work in this case but there was extensive discussion about this article last year: https://news.ycombinator.com/item?id=23966778 https://news.ycombinator.com/item?id=23966778 tldr: The top comments mentioned corporate lawyers concluding AGPL ("corresponding source") was too much of a risk and subsequent replies debate about it being FUD. I also ran across an blog article (by an attorney who writes about open source licensing) saying AGPL can be hard to understand: https://writing.kemitchell.com/2021/01/24/Reading-AGPL.html https://writing.kemitchell.com/2021/01/24/Reading-AGPL.html
- aaron695 5y ago> all you have to do is provide a link to the upstream source code somewhere, Again this is not true, another blog telling us all about AGPL who doesn't understand it. You don't have to provide source unless you as the host modified it. Read it for yourself -https://www.gnu.org/licenses/agpl-3.0.en.html https://www.gnu.org/licenses/agpl-3.0.en.html This race to abuse AGPL to attack a website is pretty much the state of IT and licensing. Very clever they made a mistake so you get to use AGPL against it's intent to attack them, the IT community is just the lousy RIAA and MPAA. I just hope they are clever back and refuse to hand the code over through their clear legal loophole. If the host bought modified code from a consultant they don't have to share that code and neither does the consultant.
- donatj 5y agoIf you were an architect, would you let your builders use nails from a manufacturer that required the designs of your buildings be released if a single said nail was laid? Even having that nail in my tool chest is a liability. I wouldn’t buy those nails to begin with.
- cylinder714 5y agoThat requirement would not be legally enforceable because nails are generic items. One cannot argue that all C programs must be GPL'd because GCC or Emacs uses main() or malloc().
- stared 5y agoHow does it relate to GPL? In GPL, as far as I understand, if you release a product containing GPL-licensed software, the whole product needs to get released as GPL. Some people love this copyleft approach (RMS), some hate it (as it is a viral license, "infecting" other parts of the codebase). For using it is a library, it is usually a no-go (for virtually all commercial products, and any open source project that wants to keep a more permissive license, e.g. MIT). > The Free Software Foundation (which holds the copyright of several notable GPL-licensed software products and of the license text itself) asserts that an executable that uses a dynamically linked library is indeed a derivative work. LGPL seems to make (IMHO a very sane and desirable) distinction: > A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. How does AGPL approach this subject? Or rather - is it closer to GPL or LGPL, when it comes to the definition of "derivative works"? (I am not a lawyer; quotations are from Wikipedia)
- garaetjjte 5y agoAGPL uses GPL wording, it is basically GPL with extra clause. However, just because FSF thinks linking is enough to make derivative work doesn't mean it necessarily is. I have come to think that GPL isn't good license because of how horribly underspecified it is in that regard.
- stared 5y agoLaweyers tend go on "the safer side" so to include the most broad definition of "derivative". (As in general: the most pessimistic interpretation of any underspecified clause.) For example, in principle a screenshot would be a perfect example of a "fair use" for citation/reference. In practice, lwayers tend to disagtee - as "a small part of a work" is something horribly unspecified. Of course, if you are Google/Facebook/Apple or so, you can do as you wish. (Unless you are at risk of a legal war with another corporation.) So because they use it in a given way does not mean that you will be able to defend yourself the same way.
- 5y ago
- derkoe 5y agoMinIO has switched their license to AGPL (the community is not happy https://github.com/minio/minio/issues/12143 https://github.com/minio/minio/issues/12143). The company behind the project is now contacting all users and tells them to pay for the commercial license. They try to make the users feels insecure about the way they use the product. They don't tell you that you are violating the license, they tell you to check with your legal, etc. So most companies will finally just buy it. This is also a way the AGPL is used: commercial interest, not user freedom.
- _vbnz 5y agoAnd what's wrong with that? At the end of the day, they need revenue to continue development. And this is a good balance between allowing FOSS use-cases whilst not allowing free-loading from proprietary, commercial uses.
- pabs3 5y agoIts unethical to scare people into a commercial license when the AGPL license is good enough for them.
- derkoe 5y agoI understand the need for revenue but starting your commercial relationship with a fraud will not turn out well. I think it would better to show the benefits of buying a license like support or influence in development.
- haukem 5y agoThe main difference between the GPL v3 and the AGPL v3 is this addition: > 13. Remote Network Interaction; Use with the GNU General Public License. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. Here is the full diff between the two license texts: https://www.diffchecker.com/cV5JfP5H https://www.diffchecker.com/cV5JfP5H
- tzs 5y agoI dislike AGPL for 2 reasons. 1. Every major free software license I can think of before AGPL triggered its source provisions on distribution. (I said "major" because I haven't examined every free software license, but I don't actually know of any that weren't triggered solely by distribution). Placing conditions in your license on what you did with the software other than distributing it were usually considered to make your license a non-free license. 2. I can't think of a principled way to justify AGPL's triggering specifically on "remote interaction through a computer network". Say I take a weather model program that is under AGPL, modify it to work better for forecasting weather in my region, and start a service to provide local forecasts. Users provide their address, and for a fee I provide them with a local forecast for that location. There are several different ways I might offer this service. A. They can stop by my kiosk in the mall, where I have several PCs running the model. They can enter their information on one of the PCs and it prints their forecast on a printer connected directly to the PC. B. They can send me a mail via the post office asking for a forecast. I mail one back via the post office. C. They can send me an email asking for a forecast. I email one back. D. Same as A, except the printer is not connected directly to the PC. It is connected via a WiFi network. E. I have one PC in the kiosk, with several terminals connected to it via WiFi. The customers use the terminals. F. Similar to E, but I have the terminals spread out at several convenient locations throughout the mall, all communicating via WiFi with the PC running the model. G. The PC serves a web page via a public WiFi network I offer in the mall. This network has no internet connectivity. H. The PC serves a web page over the internet, but you have to be at the kiosk to actually order and receive a forecast. I. The PC serves a web page over the internet, on which you can order and receive you forecast from anywhere. J. The call me on the phone, give me their address, and I read the results to them. This is really 3 cases. J1, they and I are using modern cell phones. J2, they and I are using modern land lines. J3, we are both in an area with a very old all analog phone system (so while the phone system may be a network, it is not a "computer network"). Under AGPL I definitely have to provide source for case I. It is not clear for cases C, D, E, F, G, H, or J. They all raise questions of what is an interaction, what is remote, what is a computer, what is a network, and what is a computer network. I do not have to provide source in cases A and B. In all cases the same overall thing is being accomplished: people ask for a forecast using the modified AGPL program running on my computer, the program runs, and the output is given to the person. I find it aesthetically displeasing and philosophically ridiculous to have a license depend so much on the minutia of exactly how the information between the user and the program is transmitted.
- redis_mlc 5y agoFor the nerds here ... You may understand the various licenses and their limitations, if even fuzzily. But whenever I talk to business owners, they're shocked at the terms in GPL and AGPL. I don't mean surprised, I mean shocked - they thought the code was "free" with no attribution or distribution requirements, and are deeply upset. Typically they say, "Why didn't anybody tell me? How did this happen?" And it becomes a big deal when told they need to distribute any of their code. At Apple, their policy for decades was to not use GPL software. When they bought other companies, the first thing they did was to rewrite any software even touching the GPL. Note that MySQL is used everywhere across Apple now, so that's one exception that I can think of, but they can get a license from Oracle (Apple has a close contractual relationship with Oracle, from decades of Oracle Enterprise porting, and internal distribution, and MRP products.) Note that MySQL AB re-licensed their client library from a permissive license to GPL to drive revenue from their dual licensing strategy. There is an old fork available. Source: ex-Apple.