What is Nostr?
fanf42 /
npub1ctu…kas2
2025-01-20 06:48:23
in reply to nevent1q…uj8w

fanf42 on Nostr: Tadano nprofile1q…7mzfz nprofile1q…k2mmz skylar (punished by postgresql) I don't ...

Tadano (nprofile…cjhw) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqetsgu4f780463phh0f6zd0qf8ea9rymy5c5njrkufwn4s2k3emwqm7mzfz (nprofile…mzfz) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqv7j7dtmgl6a3mhh3mhltcvlpzah8j9kh8scj7759t96mclrld44s9k2mmz (nprofile…2mmz) skylar (punished by postgresql) (nprofile…7kv5) I don't know the soft nor the details, so take it with big salt because details matter in these things.
AGPLv3 and GPLv3 can grant some permission thanks to section 7, like allowing binding with third party code (like a plugin) without changing its license. The whole program has network properties of AGPL, including the soft in a bigger one triggers the (A)GPL, but you can have non (A)GPL modules.
This is the same section allowing a compiler to produce non-AGPL code for ex.

Still, it means that you can't put arbitrary barriers in the AGPL code without people being angry and removing them, or remove features without people putting them back in a fork, as in any free software.

And for the company doing that, I would look at their governance model: if they are VC funded/part of Big Corp, the whole floss part is likely just public relations in any case, and that model ir a pure AGPL is not a very strong clue: there's a lot of cases where it happened in the last years, with whole code base going dark. See for example the recent case for Puppet.
Well actually, whatever the governance, a company doing that is not a free software good citizen.
Author Public Key
npub1ctudfsjjpgu3exmx8t69mwztam2q0kpwh9h77h9ngs00jnzlgn2q8ykas2