permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 72ec1103069f3fd57fc76cce969fd45335ccf534
parent ae67201f1d7f1f510da139da187df4ab94b9e675
Author: ugrnm <ugrnm@web>
Date:   Sun,  8 Nov 2026 13:49:53 +0100


Diffstat:
MFLOSS.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FLOSS.mdwn b/FLOSS.mdwn @@ -7,6 +7,6 @@ The two major definitions of FLOSS are free software and open source software. T While a popular method for software production and distribution, FLOSS has been increasingly scrutinised for its underlying ultraliberal and libertarian ideologies that have been more useful to the ICT industry, than it has been useful to foster the much anticipated digital commons of public interest, as envisioned in the late 90s and 00s. This is because both free software and open source software proponents support the idea of permitting the (re)use of FLOSS source code for *any* purpose. As a result a growing number of post-free culture licenses have started to emerge in the late 10s and early 20s to address issues of ethics and exploitation found in the *for any purpose* take of FLOSS.[^nocommons] -**Consequently, permacomputing practices, while frequently using and generating FLOSS projects, remain highly critical of this approach. We do not accept the FSF tactic of dismissing critiques, avoiding the hard discussions on dual-use technology and social harm, because it is inconvenient or incompatible with software freedom. As a result, permacomputing does not see FLOSS as a de-facto solution, but only as *one* of many different already existing, or yet-to-be-invented approaches for sharing and producing digital culture.** +**Consequently, permacomputing practices, while frequently using and generating FLOSS projects, remain highly critical of this approach. We do not accept the FSF and librists tactic of dismissing critiques and avoiding the hard discussions about dual-use technology and social harm, simply because it is inconvenient or incompatible with software freedom. As a result, permacomputing does not see FLOSS as a de-facto solution, but only as *one* of many different already existing, or yet-to-be-invented approaches for sharing and producing digital culture.** [^nocommons]: See Aymeric Mansoux, "Nothing in Commons: the end of digital collective ownership?", 2025, [https://collectiefeigendom.nl/en/ownership/digital-collective-ownership](https://collectiefeigendom.nl/en/ownership/digital-collective-ownership).