Earlier quoted context omitted.
I was thinking the same. It being published on GitHub makes it especially difficult to claim damages for reuse, as I think it’s fair to say the very act of publishing to GitHub implies a desire to share the code. The real issue would be if the author decides they want to close source it later, updates the license, and then demands everyone stop using it.
> the very act of publishing to GitHub implies a desire to share the code. No. Thats like saying the very act of sharing pictures online implies you want someone else to use them, or that printing your book and selling it somehow implies you want the world to copy it. You share on GitHub because its a source control platform, and your code may be interesting to others. This does NOT mean that you are okay with someon…
Please explain how you are viewing this unlicensed reply without downloading it.
> You share on GitHub because its a source control platform, and your code may be interesting to others. This does NOT mean that you are okay with someone taking the code and using it in their (potentially commercial) program.
Please explain how HN is not taking my unlicensed reply and using it in their commercial HTML code sent to your web browser.