Yes, well, I have many software projects that are well-known, so I am cursed with a good problem to have. I therefore must balance my ideology with pragmatism.

Yes, well, I have many software projects that are well-known, so I am cursed with a good problem to have. I therefore must balance my ideology with pragmatism. I was a little coy above. I said that I "release my code into the public domain to the extent possible." In practice, I dual license my code under the UNLICENSE (public domain, effectively) and the MIT. I do this because the UNLICENSE is unsuitable either because people are too risk averse for it or because public domain is for one reason or another not recognized in their jurisdiction. I didn't elaborate on this in my original comment because it's not really pertinent. I think. But yes, I can't put code out there without a license because I ultimately want people to use it. And I've made the mistake of using a license that people don't like to use before (the WTFPL). You do indeed get bugged quite a bit.