4 ms·

Thanks for your detailed reply, I read it carefully. Let's stay on imagemagick, except we pretend it has an AGPL license (that's not it's actual license, but t

Thanks for your detailed reply, I read it carefully. Let's stay on imagemagick, except we pretend it has an AGPL license (that's not it's actual license, but this is the example I want to stick to.) So under these conditions: if you have a server where you upload a picture of yourself, and it shows how you will look in 20 years, and the server does this by making actual modifications to imagemagick, then you don't think I have to publish my changes to imagemagick? I mean if I dig into the AGPL source code and really modify the whole program to do what I want/need. I can keep those modifications private, in your opinion? While even selling the output?

singron 7y ago
If you keep your modified imagemagick a separate program from the server that interacts with users (and don't e.g. exchange complex internal datastructures over IPC between imagemagick and the server) then it seems fine. If you add network interactivity directly to imagemagick then no. I wouldn't worry too much about this case in practice because there are very few programs that choose the AGPL and don't have network interactivity.