I’m planning to open-source soon—ideally it’s eventually a protocol, not a centralized service! (Once we figure out what “it” is…)
I’m trying to balance benefit to the commons with retaining some privilege/flexibility. Tell me why this licensing plan is a bad idea?
Conversation
Love this! I’m strongly considering a similar approach for Subconscious. I would love to share notes and learn from your experience with this approach.
1
4
I think the biggest objection to this approach is that it’s very highly centralized. The BDFL controls the trademark, the domain names (crucial for a cloud service), and the asymmetric privilege to re-license commercially. Arguably it’s letter-but-not-spirit OSS.
Yeah, I'm all about license experimentation. GPL's cloud loophole spoils most of the chaotic-good energy of viral licensing in this era of cloud aggregators. Experiments like AGPL, SSPL are bringing back some of that energy.
1
2
👀 Following this convo
2