[kemitchell]

I appreciate this feedback. Maybe it won't surprise to read we definitely thought about this!

Certainly for 2022, we could look around at how software gets made and distributed and try to spell out something more specific. In package metadata. In README. In a COMMERCIAL file. In the repo on lines with a magic string stated in the license. But for better and worse, we've learned to stay humble making assumptions about how those things will continue to happen in software development and distribution. Everything's subject to unexpected change.

In the end, we had to be conservative with this, since "breakage" in the contact method could effectively make the software permissive. Once you put software out there with license terms attached, you can't go back five years later and hunt down all the copies people have made, on the Internet and privately.