A minor typo clarification in
@nextcloud's post (which I otherwise agree with). I'm not the sole author of any version of #AGPL. I invented the method that makes the Affero clause work¹, and I helped codraft #AGPLv3§13.

License drafting has many contributors; no one is the sole "author".

¹ I invented the approach of an additional requirement when modifying the software that the complete, Corresponding Source be made available to all who had access to the running software.

#AGPLv3

As many raise questions about #EuroOffice and the #AGPL license ( @nextcloud #Ionos...) my current recommendation is to read:

* @fsf 's "You cannot use the #GNU (A)GPL to take #softwarefreedom away fsf.org/blogs/licensing/agpl-i…

* and @bkuhn 's "#AGPL v3§7¶4 Empowers Users to Thwart #Badgeware" sfconservancy.org/blog/2026/ap…

AGPLv3§7¶4 Empowers Users to Thwart Badgeware

This article discusses a current-headlines situation regarding Affero General Public License, version 3, Section 3, paragraph 4 (AGPLv3§7¶4.). I begin however with an explanation of the problem that clause sought to solve and how the clause works.

^{Software Freedom Conservancy}