@tylor @AilesGrises The thing is, the AGPLv3 only kicks in when:
(a) *You* have modified the software.
(b) The software is being interacted with by remote users.

"13. Remote Network Interaction; Use with the GNU General Public License.

Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software."

If you haven't modified the server software, you don't need to provide the source code, as after all, the user can just download that from the developer.


I guess a HTTP server usually performs user interaction, as the user browses to the site and can also click links on the site to go to other pages.

AGPLv3'd p2p software installed on a users computer probably isn't subject to the AGPLv3's additional terms, as long as such doesn't offer remote interaction to other users.

One example would be a torrent client, in which the user merely adds a magnet link and the software uninteractively communicates with the other peers.

Meanwhile, if you were to take that torrent client software and turn it into SaaSS, as offer the users a remote interface to interactively upload a magnet link and download completed files, the AGPLv3's terms will kick in.