Many users of AGPL contend that if you connect to their AGPL code by API, your entire application needs to share its entire source code (including to anyone who

Many users of AGPL contend that if you connect to their AGPL code by API, your entire application needs to share its entire source code (including to anyone who accesses it over a network/internet.) For example, the founder of iText feels very strongly about this. As you can imagine, that makes iText almost impossible to use in a commercial setting, if you want their AGPL version. You need to buy their commercially licensed version. "If user A pushes a button in product X, and by doing a technical effect is triggered that results in an action in (A)GPL library Y, then product X needs to be released under the same license as library Y to user A no matter how product X is technically implemented!" https://entreprenerd.lowagie.com/chapters/c13.html https://entreprenerd.lowagie.com/chapters/c13.html https://itextpdf.com/how-buy/AGPLv3-license https://itextpdf.com/how-buy/AGPLv3-license https://entreprenerd.lowagie.com/ossurvival/index.html https://entreprenerd.lowagie.com/ossurvival/index.html https://www.slideshare.net/iTextPDF/ianal-what-developers-should-know-about-ip-and-legal https://www.slideshare.net/iTextPDF/ianal-what-developers-sh... https://opensource.stackexchange.com/a/6904 https://opensource.stackexchange.com/a/6904