Hi,
IANAL as well, but the intent of the AGPL is that if you host the
software on a server in a modified form (e.g. you run a cloud node) then
you also have to publish the modified source code even if you did not
distribute the program (you only offered the service through an API).
Now, "using" the software comes in different flavours.
Of course, linking against a GPL library (e.g. libgnunetutil) will
require you to license your program under the AGPL as well.
But, communication with a gnunet node (i.e. the AGPLed reference
implementation) through the open API (ports or REST API) usually does
not require you to AGPL the code of your application (or publish it).
I may be wrong, but that is my interpretation.
BR
Martin
On 15.11.23 14:42, Augusto A. Cognigni wrote:
I'm not a lawyer so I'm asking you.
Since gnunet is under AGPL does that mean that any site or application I
develop that uses gnunet has to be AGPL? Or it can be closed source?
Enviado desde Proton Mail móvil
