The use case for MPL and SSPL was broadly the same: selectively apply permissivity for the primary build-on use case (browser plugins, applications) to stoke ad

The use case for MPL and SSPL was broadly the same: selectively apply permissivity for the primary build-on use case (browser plugins, applications) to stoke adoption and copyleft to other use cases (forks, hosted offerings) as a bulwark against competitors (Microsoft, AWS). In drafting and presentation, I thought SSPL failed to communicate that heritage. So I wrote what became the API Copyleft License.