4 ms·

Why? Does AGPL really matter if you're not planning on monetising whatever it is you're using it for? Not trying to be snarky, I'm genuinely curious why you'd

Why? Does AGPL really matter if you're not planning on monetising whatever it is you're using it for? Not trying to be snarky, I'm genuinely curious why you'd be so vehemently opposed to it.

Aeolun 2y ago
I think the crux of the argument is that if you are not planning to monetize it, why stop other people from doing so?
- andrewstuart 2y ago
  Also, is there really any money left in message queues? Every man and his dog has made a message queue with Postgres. Message queues are everywhere on github and often posted on HN.
- meiraleal 2y ago
  AGPL don't stop nobody from monetizing anything, they just gotta make their modifications public.
  - pc86 2y ago
    If you're anywhere close to a technical or developer space it's pretty clear how making your entire codebase public could negatively impact a monetization strategy. So yeah you're right that AGPL doesn't explicitly prevent monetization (other than "pay us for the source code" stuff of course) but in practice nobody with a serious monetization strategy is going to be releasing all their code AGPL either.
    - meiraleal 2y ago
      > but in practice nobody with a serious monetization strategy is going to be releasing all their code AGPL Which fulfills the developer will of attracting higher quality users that plan to collaborate with him. You got it right :) You got something wrong tho, If you're anywhere close to a free software/open source space, you should know that using his AGPL SQS replacement, the only thing that would need to be public is whatever you change in it, not the things you use it.
ahachete 2y ago
AGPL is the best OSS license to ensure project continuity as Open Source. That simple. Permissive licenses allow for proprietary forks, which may become more successful than the upstream project. AGPL would be able to benefit from any improvements from any fork, and all those will remain OSS for everyone. Nothing written here is related in any way to monetization.

Why? Does AGPL really matter if you're not planning on monetising whatever it is you're using it for? Not trying to be snarky, I'm genuinely curious why you'd be so vehemently opposed to it.

Aeolun 2y ago

I think the crux of the argument is that if you are not planning to monetize it, why stop other people from doing so?

andrewstuart 2y ago
Also, is there really any money left in message queues? Every man and his dog has made a message queue with Postgres. Message queues are everywhere on github and often posted on HN.
meiraleal 2y ago
AGPL don't stop nobody from monetizing anything, they just gotta make their modifications public.
- pc86 2y ago
  If you're anywhere close to a technical or developer space it's pretty clear how making your entire codebase public could negatively impact a monetization strategy. So yeah you're right that AGPL doesn't explicitly prevent monetization (other than "pay us for the source code" stuff of course) but in practice nobody with a serious monetization strategy is going to be releasing all their code AGPL either.
  - meiraleal 2y ago
    > but in practice nobody with a serious monetization strategy is going to be releasing all their code AGPL Which fulfills the developer will of attracting higher quality users that plan to collaborate with him. You got it right :) You got something wrong tho, If you're anywhere close to a free software/open source space, you should know that using his AGPL SQS replacement, the only thing that would need to be public is whatever you change in it, not the things you use it.

ahachete 2y ago

AGPL is the best OSS license to ensure project continuity as Open Source. That simple. Permissive licenses allow for proprietary forks, which may become more successful than the upstream project. AGPL would be able to benefit from any improvements from any fork, and all those will remain OSS for everyone. Nothing written here is related in any way to monetization.