Why I have trouble trusting FSF
Why I have trouble trusting FSF
Posted Aug 11, 2011 8:18 UTC (Thu) by AlexHudson (guest, #41828)In reply to: Why I have trouble trusting FSF by ballombe
Parent article: Desktop Summit: Copyright assignments
Similarly, using a reverse proxy to circumvent the license restriction is pretty obviously an infringement of copyright. I can't think of many circumstances where a court would fail to treat that the same as stripping the feature out, because that's what you're doing. The technical means to achieve that are totally irrelevant.
Posted Aug 11, 2011 12:22 UTC (Thu)
by gidoca (subscriber, #62438)
[Link] (3 responses)
Posted Aug 11, 2011 14:25 UTC (Thu)
by davide.del.vento (guest, #59196)
[Link] (2 responses)
If you use my AGPL source code into your application, even if you do not distribute it in the "traditional" sense (but have users using it "remotely, e.g. as a web application), then you *must* provide the whole source code that it's running. If it's just mine, fine, but if you made any modification, or if you linked anything else that was yours, you have to provide that too.
Posted Aug 11, 2011 15:40 UTC (Thu)
by gidoca (subscriber, #62438)
[Link]
Posted Aug 13, 2011 5:02 UTC (Sat)
by dberlin (subscriber, #24694)
[Link]
Why I have trouble trusting FSF
I wonder what this means with respect to the AGPL-licenced iText library. The terms of use page (http://www.itextpdf.com/terms-of-use/index.php) seems to imply that you have to provide the source code of a web application that uses iText, but I don't think the AGPL requires this.
Why I have trouble trusting FSF
Why I have trouble trusting FSF
Why I have trouble trusting FSF
The AGPLv3 *only* requires you distribute source to users interacting over a network if you modify the program.