> That doesn't seem to be quite right. It makes it sound like the source code entitlement applies to all users. The "including users accessing it over the netwo

> That doesn't seem to be quite right. It makes it sound like the source code entitlement applies to all users. The "including users accessing it over the network" is redundant then because they are a subset of all users. The AGPL is written in the context of the gpl, where user is someone who runs the software. The AGPL extends this to someone who uses the software over the network. You're right that that kind of means "all users" - but let's take the example of a GPS appliance - if you buy the device, and run software on in, you're a "gpl user". If the appliance is a server that runs a web application - the person operating the appliance is a "gpl user", the one interacting with it via the web is not - but they are an "AGPL user". If you relay directions to someone (say as a passenger/navigator in a car) - you could argue the driver also "uses" the software - but only the passenger would be considered an "AGPL user". All this must be seen in light of the four freedoms, and who it applies to (who is a user). The AGPL extends freedom zero (the freedom to run the software) - to those accessing it over the network - in short, it grants the right to self-host and run the code.