commit 37c1f20245b9f182c393593173897ebd7273f848
parent 0639bc03e9b5d8e61c923e6beb51aa166bdfd781
Author: ugrnm <ugrnm@web>
Date: Sat, 6 Dec 2025 13:38:17 +0100
empty web commit
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/FLOSS.mdwn b/FLOSS.mdwn
@@ -11,4 +11,4 @@ While a popular method for software production and distribution, FLOSS has been
As a result, permacomputing practices, while frequently using and generating FLOSS projects, remain highly critical of this approach. Permacomputing does not see FLOSS as a de-facto solution, but one of many relevant approaches for software production and distribution.
-[^nocommons]: See Aymeric Mansoux, "Nothing in Commons: the end of digital collective ownership?", 2025, [https://collectiefeigendom.nl/en/ownership/digital-collective-ownership](parenthesis could be used as well, sure, or long — em dashes, but if you're going to fork the discussion to something that's too long to fit in the flow of the main text, and that does not need its own page, then a footnote can be quite handy).
+[^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).
