Hacker News new | ask | show | jobs
by appleflaxen 1081 days ago
Consider whether you might want to release it as AGPL3, and offer a proprietary license for a fee.

That prevents a private company from forking a closed source version without paying you.

2 comments

I thought the community hates AGPL3. I'm not sure why forking and setting env varaible as OPEN_SOURCE=true would be a hard thing to do.
They do, because many in HN are entrepreneurs building platforms that don't want to open source their products that incorporate your code.

What authors don't realize is that they can still do that if you let them pay for a non GPL version.

I made it AGPL3 after your suggestion. Now everyone is happy I suppose