55
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Sep 2025
55 points (98.2% liked)
Open Source
41195 readers
788 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
The reason for the creation of AGPL is not "limiting" commercial use. It's there, so that a company commercially using your AGPL project is also required to publish its changes under AGPL, even if the only way they "distribute" the software is as a Application Service Procider (SaaS company). Because under regular GPL, this case wasn't covered, so big companies could use your code, modify it, offer it as a SaaS product and NOT publish their changes unter a free license.
AGPL specifically exists, so the rules around commercial SaaS use are clear – so I'd argue it's the opposite of "limiting commercial use".
See: https://yairudi.com/understanding-asp-loophole/
Sorry yea bad wording on my part, I was intending "limiting" to refer to stopping companys from profiting off of your work without limits (controbuting back to the comminity)