> There are plenty of ways that you could let users communicate with a program on your server that do not involve remote communication through a computer network.
There are a couple of categories of ways to communicate that would not involve remote communications through a computer network.
One category is communication that is not through a computer network, such as through serial terminals or by voice.
Another category would be communication that is not remote. AGPL fails to define what it means by "interacting remotely", but where they use that phrase is in a section titled "Remote Network Interaction" which suggests they are using "remote" the way people generally use it in the context of networks. Remote in that context means generally not on the same LAN. If that's the case then while communication over the LAN would be over a computer network it would not be remote communication.
these don't seem to be the common cases that matter today - big corps taking open source code and making big money off them without giving anything back to the community and instead occasionally hound at lone developers for timely fixes so they can keep on making the big money.
One category is communication that is not through a computer network, such as through serial terminals or by voice.
Another category would be communication that is not remote. AGPL fails to define what it means by "interacting remotely", but where they use that phrase is in a section titled "Remote Network Interaction" which suggests they are using "remote" the way people generally use it in the context of networks. Remote in that context means generally not on the same LAN. If that's the case then while communication over the LAN would be over a computer network it would not be remote communication.