UPDATE: after reading
this post, I'm realizing that the idea below falls into a similar
selfsabotaging non-
OSI
fringe-trap.
Just like the SSPL License.
I still strongly
believe in symmetric
use
of commons, persons, hardware, software and networks
, however promoting it seems more appropriate
elsewhere
in a post-growth company or nonprofit org, rather than a toolbox-level.
Copyleft
, a type of open-source license that require derivative works to be distributed under the same license terms as the original work, ensuring that the software and its modifications remain freely available. Basically copyleft
AND copyright software licenses both promote asymmetric infinite growth
, typically by scaling client-server-style solutions via serverparks
.
Don't get me wrong: growth is great (until it's not).
Pluralism and ecology is better.
Many of us are not aware of the observation by Michel Bauwens:
"The more communist the license, the more capitalist the practice"
For example, AGPL or SSPL-licensing code is actually entropic and
pseudo-protective.
Because companies or individuals promoting commons at the front door, are not prevented dual-licensing at the backdoor (to companies). This enables
one-dollar-one-vote
, instead of one-person-one-vote (the idea of commons).
This is how commons get 'enclosed' or overtaken by companies (is this the altruistic fate of commons?)).
Instead, how far-fetched is
it
at least for Europeans, Chinese, East-asians, Latin Americans, Indian, South Africans: these legal systems judge things based on spirit-of-the-law, rather than strict letter-of-the-law (like the US). Therefore it is not futile
, to add an license clause (see draft below) to a software license, that promotes conditional, symmetric commercialisation based on architecture (not reactive governance):
=======================================================================
Additional Terms and Conditions
Conditional Commercial use is allowed, when the original work, copy or adaptation follow these symmetric requirements, to ensure symmetric syntropic commons:
1. Open Technology Reciprocity Requirement
All technologies and adaptations, should use or extend Open Commons (Opensource software, Open Internet Standards, Specifications or (RFC) Drafts) and should be made available to the public via mainstream URLs. This also includes disclosing full REPRODUCIBILITY of data used to develop and operate the work or adaption, except for typical data (like multimedia) that does not impede the transparency of the work or adaptation.
2. Offline-First Requirement:
All adaptations and commercial deployments must adhere to the Offline-First principle. This means the software or content must primarily function without requiring a continuous internet connection and should not depend on a centralized server (Client-to-Server or C2S architecture) for core functionalities. P2P (Peer-to-Peer) or DAPP (Decentralized Application) data exchange features are permitted, but they must not replace the offline-first functionality.
3. Online P2P-second Requirement for networking:
All adaptations and commercial deployments must ensure that feature-symmetry between offline- and online usage is always maintained. Transmission of userdata must be Offline-first, P2P-second (sending/receiving/importing/exporting userdata e.g.) as Decentralized Applications (Dapps). The user experience, or solution-discovery should never revert or depend on a predominantly centralized server-architecture (C2S, client-server). This condition is intended to promote network symmetry and environmental sustainability, contrasting with traditional centralized cloud platforms (datastorage), like asymmetric serverpark-heavy strategies used in the 90s for social media, music players, or other services.
4. Symmetric monetization requirement:
All forms of monetization must be symmetric, consent- and revenue-split driven: monetizing P2P userdata (psuedonymous, anonymous, explicit), or advertising revenue should be split by the user. Symmetry of advertisements needs to be maintained, by alternating between commercial and commons advertisements. All forms of monetization-features should be first-mover-advantage-agnostic, by ensuring equality between new users and early users.
5. Non-Relicensable Requirement:
All forms of relicensing (dual-licensing, additional contributor licenses) are prohibited as they break the symmetry between contributors and non-contributors of the solution or adaptation.
These additional terms are supplementary to the [COPYLEFT LICENSE HERE] License and do not override its terms. All users must comply with both the base license and these additional terms.
In a nutshell: commercialisation is allowed as long as the solution(s) use/stay symmetrical commons: Offline-First and
P2P-second for networking (a DAPP) using
Open Technology (O), like Open Internet Standards, Open (Draft) Specifications (like RFC's) which are made available via mainstream URLs.
Meaning, it may include P2P data exchange as a feature, but this should not replace the
core requirement
of offline functionality. Any commercial deployment must respect the offline-first principle, by not allowing features to digress to a C2S (client-server) centralized server architecture.
A great example which meets the first 3 requirements is slingcode.net.
The moment a company builds a C2S-layer on top of it (a website with user-signup, pricing e.g.), the common gets 'enclosed' (hence requirement 4 & 5).
Symmetric Opensource Collaboration using symmetric agreements could potentially promote greener, by reducing serverparks user/network/hardware/company symmetry and interoperability. In contrast to asymmetric apps like 90s centralized cloudplatforms for social media, musicplayer, or LLM's.
By promoting symmetric commercialisation-agreements, we might foster symmetric commercialisation of software, benefiting both user, commons, companies and planet (Leon van Kammen)