@drewdevault@fosstodon.org You're right, but part of why I am being strict about this is that I once worked for a company in the acronym "ANTMAMA", and this company had a rule you could not use open source unless the license was on their approved list. This approved list had over a thousand licenses, but at one point I had reason to use a library whose license (the WTFPL) was not on the list, and so I wasted time incorporating the library, then consulting with legal, tearing the library out, and replacing it.
@drewdevault@fosstodon.org I'd like my code to be useful! If I'm not helping the person I give the code to, why bother?
I think I do have options, such as: Homebrew a license, then say "or, at your option, 2-clause BSD"; or use 1-clause bsd with *separate explanatory text* indicating how I intend the license to be interpreted, which probably creates a "meeting of the minds"(???) for purposes of contract law. But this is all very awkward, so so far when I'm tempted to do this I've wound up just using CC0.
@drewdevault@fosstodon.org Anyway, thanks for your thoughts!