2 ms·
In short: It prohibits you from not sharing your code based on whether or not the ethernet cable is or is not plugged in to your machine. This is like nonfree
by sneak 4y ago
In short: It prohibits you from not sharing your code based on whether or not the ethernet cable is or is not plugged in to your machine.
This is like nonfree usage restrictions on otherwise free software, like the famous (if unenforceable) “can not be used for evil” license clause.
- bawolff 4y agoRight but which freedom does that restrict that's not in the spirit of the gpl? I.e. the gpl prohibits you not sharing code if you distribute the binary. What is the philosophical underpinning of "sharing binary" not being a restriction but "ethernet" being a restriction. The evil thing is not similar because you are discriminating against a field of endevour (similar to licenses that say educational use only, non-commercial only or non-military only). It seems to be a very different type of restriction.
- em-bee 4y agothat's not right. in my understanding the intention of the AGPL is to share code with users of a program, even if the users didn't get a copy of the program. therefore the AGPL shouldn't force you to share code if the program runs on a server. but it should force you to share code if the program can be accessed by a user. this may even apply to running something like a kiosk device where users interact with a program on a device they don't own.
- the_gipsy 4y ago> whether or not the ethernet cable is or is not plugged in to your machine That's not even remotely near what it is.