commit 42531120e76539716488597d88b16e703a2c7449
parent 2f7c917ad68d47cd5c9331c47c49b1a3d5e85f21
Author: ugrnm <ultrageranium@bleu255.com>
Date: Mon, 5 Jan 2026 10:05:15 +0100
Merge branch 'master' of borok:/var/www/git.bleu255.com/repos/permacomputing
Diffstat:
9 files changed, 53 insertions(+), 47 deletions(-)
diff --git a/FLOSS.mdwn b/FLOSS.mdwn
@@ -7,4 +7,8 @@ The two major definitions of FLOSS are free software and open source software. T
* (strong, weak) copyleft licenses. Such licenses impose the person making modification to copyleft material to share their modification under the same condition/license than the code they modified. The idea is to promote circulation and virality;
* permissive or copyfree/copycentre licenses. Such licenses have much more simple conditions for reuse, if any, making possible to use such source for closed source software and proprietary systems.
-While a popular method for software production and distribution, FLOSS has been increasingly scrutinised for its underlying liberal, possibly ultra-liberal ideology that has been more useful to the for-profit software 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.
+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]
+
+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 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).
diff --git a/add_the_starter.mdwn b/add_the_starter.mdwn
@@ -1,4 +1,4 @@
-Add the starter
+Add the Starter
===============
Gather people, build rhythm, and set gentle infrastructure.
@@ -20,15 +20,16 @@ than scale.
**Quotes**
> It was meant to be a single event, but people asked if it was recurring — so it became weekly.[...] Because it’s weekly, it feels non-committal, but consistent enough for reflection. — Ana, London
-
+<!-- -->
> Start small — a table, four people, and an idea is enough. [...] We announce it as an informal meetup so people feel they can just come, drink something, and talk. — Brendan, Berlin
-
+<!-- -->
> It’s not a workshop — it’s a living situation. People do what they like, together. — Michal, Prague
-
+<!-- -->
> Our spaces of gathering are completely digital. Our main one is an XMPP group, where we discuss and share constantly. We also publish in our social network (Akkoma) to know more about our daily lives. Finally, and more rarely, we use Mumble to hear our voices and chat. — Archipiélago I
-
+<!-- -->
> A lot of people just are intrigued by the idea actually. I've had a lot of conversations where I'm selling somebody a book and they look at the flyer and they say “what is permacomputing?” and I go into my little spiel. People want to learn more about this stuff. — Steve, Philadelphia
-
+<!-- -->
> Here people interested in permacomputing are those who live the most remotely because they have a need for a kind of resilience. At least in Ireland, that's what I've noticed. When I ran the online [workshop], I was expecting a bigger diversity of people in terms of geography but I was wrong. People from even further away [joined] and they were glad to be able to join online. [...] there are lots of people who literally, as soon as there is a minor storm, lose power and they lose Internet. [...] So, it's really a question of need. — Colm, County Mayo
-
+<!-- -->
> Somebody – a very nice person who studies at HKU (Utrecht School of the Arts) and is traveling at the moment, came by Varia and had a lot of energy and time and was keen to start it. Then we made a Signal group and a little pad. — crunk and d1, Rotterdam
+<!-- -->
diff --git a/brew_the_base.mdwn b/brew_the_base.mdwn
@@ -1,4 +1,4 @@
-Brew the base
+Brew the Base
=============
Find your main ingredients, intentions, and inspiring places.
@@ -22,15 +22,16 @@ dominant and extractive forms computational culture.
**Quotes**
> I fell into coding as a teenager, but I came into permacomputing through Marx and political radicalism, more than through gardening. [...] Finding a space that feels inspiring is the most important thing. It just felt right. We wanted a place that isn’t about production or efficiency, but about thinking, reflection, and care. — Ana, London
-
+<!-- -->
> I just had an itch — and felt that if I didn’t start it, it wouldn’t happen. — Brendan, Berlin
-
-> I sat down to brainstorm a digital space that would include those identities and that would also do it in the most frugal and simple way possible. I've been exploring pubnix and the smol web while reading about frugal computing and low-tech, including permacomputing. Thanks to a friend’s enthusiasm and technical assistance, by January of the following year I had the basics up and running. From there, it has slowly taken shape. — Archipiélago I
-
+<!-- -->
+> ~diez sat down to brainstorm a digital space that would include identities from Middle America, one that would be made in a frugal and simple way. They've been exploring pubnix and the smol web while reading about frugal computing and low-tech, including permacomputing. After that, and thanks to a friend’s enthusiasm and technical assistance, some months later they had the basics up and running. From there, the community has slowly taken shape. — Archipiélago I
+<!-- -->
>The actual kick-off was not due to me but to [Björn - a colleague] who said “Ok. I would be on board. If we team up, we can do it.” If I’m not alone in it and somebody else actually brings some initiative then I can see this happening, even if I’m a bit skeptical about dedicating to yet another cause. — Simon, Vienna
-
+<!-- -->
> I always wanted to do something in this area but initially I lacked the language for it until I found existent papers and discussions around permacomputing, online on Mastodon – this gave me a framework to start. — Colm, County Mayo
-
+<!-- -->
> A lot of the people who come into the bookstore and become part of this group or other groups, are working in the tech industry or some kind of job that they may have an issue with. They have these frustrations and they feel, especially at work, that they are in the minority and these topics are not welcome. So it's a bit of a breath of fresh air for some folks to just be able to talk a little more freely about their actual political beliefs. — Steve, Philadelphia
-
+<!-- -->
> We know amazing work has been done – all this practical stuff in the permacomputing community. It has been a place for people to gather and work on some sort of guiding North Star or framework for thinking about digital technology that doesn't absolutely suck. — d1 and crunk, Rotterdam
+<!-- -->
diff --git a/brewing_collectives.mdwn b/brewing_collectives.mdwn
@@ -1,11 +1,11 @@
-How to start a permacomputing collective
+How To Start a Permacomputing Collective
----------------------------------------
This is a guide brewed from conversations with initiatives in London (UK),
Berlin (DE), Prague (CZ), Philadelphia (USA), Rotterdam (NL), Vienna (AT),
Lutruwtia (Tas/AU), County Mayo (IE) and a community from Middle America
gathering on servers. This text can support you when starting a permacomputing
-collective and we [[use fermenting as a
+collective. We [[use fermenting as a
metaphor|fermenting_as_a_model_for_collective_action]]. It isn’t a strict
recipe but more of a loose framework that can be freely modified to suit local
tastes and conditions. Many actions are cyclical and can be seen as
@@ -14,9 +14,7 @@ opportunities to revisit or re-purpose later.
Start where it makes sense for you.
-* [[brew the base]]: stories about how groups started
-* [[add the starter]]: early organizing & infrastructure
-* [[let it ferment]]: governance, challenges, and ongoing culture
-* [[pour and share]]: reflections, advice, and spreading practices.
-
-[[Colophon|colophon_brewing_collectives]]
+* [[Brew the Base]]: stories about how groups started
+* [[Add the Starter]]: early organizing & infrastructure
+* [[Let It Ferment]]: governance, challenges, and ongoing culture
+* [[Pour and Share]]: reflections, advice, and spreading practices.
diff --git a/colophon_brewing_collectives.mdwn b/colophon_brewing_collectives.mdwn
@@ -3,11 +3,11 @@ Colophon
Brewing Collectives was initiated by [Aymeric Mansoux](https://post.lurk.org/@320x200) and [Brendan Howell](https://post.lurk.org/@praxeology) with support from [Error 417 Expectation Failed](https://tldr.nettime.org/@Error417).
-Text written by anna andrejew, [Brendan Howell](https://post.lurk.org/@praxeology) and [Ola Bonati](https://post.lurk.org/@latenspace), based on interviews with [Ana Meisel](https://mastodon.social/@anmeisel) (London Permacomputing Club), [Archipiélago I](https://archipielago.uno/), [Colm O'Neil](https://post.lurk.org/@colm) (Wilderland permacomputing group), [crunk](https://post.lurk.org/@cmos4040) and [d1](https://gts.varia.zone/@decentral1se) (rotterdam.permacomputing.net), [Brendan Howell](https://post.lurk.org/@praxeology) (Berlin Permacomputing Meet Up), [Michal Klodner](https://biophilicresearch.net/channel/michal) (Node9), [Nancy Mauro-Flude](https://post.lurk.org/@sister0) (Autoluminescence Institute), [Simon Repp](https://post.lurk.org/@freebliss) (permacomputing Vienna), and Steve McLaughlin (Philly permacomputing + solar punk meetup, hosted together with Dave Slinger).
+Text written by [anna andrejew](https://annaandrejew.com), [Brendan Howell](https://post.lurk.org/@praxeology) and [Ola Bonati](https://post.lurk.org/@latenspace), based on interviews with [Ana Meisel](https://mastodon.social/@anmeisel) (London Permacomputing Club), [Archipiélago I](https://archipielago.uno/), [Colm O'Neil](https://post.lurk.org/@colm) (Wilderland permacomputing group), [crunk](https://post.lurk.org/@cmos4040) and [d1](https://gts.varia.zone/@decentral1se) (rotterdam.permacomputing.net), [Brendan Howell](https://post.lurk.org/@praxeology) (Berlin Permacomputing Meet Up), [Michal Klodner](https://biophilicresearch.net/channel/michal) (Node9), [Nancy Mauro-Flude](https://post.lurk.org/@sister0) (Autoluminescence Institute), [Simon Repp](https://post.lurk.org/@freebliss) (permacomputing Vienna), and Steve McLaughlin (Philly permacomputing + solar punk meetups at [Iffy Books](https://post.lurk.org/@iffybooks), hosted together with Dave Slinger).
Copy editing and advice by [Marloes de Valk](https://post.lurk.org/@l03s) and [Aymeric Mansoux](https://post.lurk.org/@320x200).
-Web design by [ungual](https://post.lurk.org/@doriane) with illustrations from [Raquel Meyers](https://post.lurk.org/@raquelmeyers).
+Design for the dedicated website and PDF by [ungual](https://post.lurk.org/@doriane) with illustrations from [Raquel Meyers](https://post.lurk.org/@raquelmeyers).
Thanks to [Delisa Fuller](https://mastodon.gamedev.place/@kattrali) and [Dušan Barok](https://post.lurk.org/deck/@sandu) for contributing to the early permacomputing wiki to print tools and discussion :)
diff --git a/expose_the_seams.mdwn b/expose_the_seams.mdwn
@@ -31,7 +31,7 @@ What can YOU do
**When creating and maintaining software, digital tools or infrastructure**
-* Share your projects' source code, blueprints, and design philosophy.
+* Share your projects' source code, blueprints, and design philosophy. Keep in mind that openness alone is not enough, and can even work against the interests of your community. See [[FLOSS]] to learn more about the position of permacomputing in relation to the digital commons.
* Show the inner-workings whenever possible (different technical and non-technical parts of a project).
* Don't automate every aspect of a project to keep knowledge about how things work available to non-experts also.
* Sonify or visualise "background" processes that take computational resources but aren't part of an interaction.
diff --git a/fermenting_as_a_model_for_collective_action.mdwn b/fermenting_as_a_model_for_collective_action.mdwn
@@ -31,6 +31,6 @@ Like a fermentation process, this guide invites interaction and transformation.
Apply it in parts or as a whole, start where it feels right.
-Don’t panic, organize!
+Don’t panic, organise!
diff --git a/let_it_ferment.mdwn b/let_it_ferment.mdwn
@@ -1,4 +1,4 @@
-Let it ferment
+Let It Ferment
==============
Give it time. Let it self-organise. Care for contradictions. Encourage others
@@ -26,19 +26,20 @@ collective can survive the absence of its initiators.
**Quotes**
> At first I did everything — website, announcements, logistics — but over time others started hosting workshops. When I went on holiday, the group continued without me. That was a good sign. Overall I would say; start small, be okay with leading at first, and then let it grow away from you. — Ana, London
-
+<!-- -->
> It’s about seeding the ground, so others can pick it up and spread it. The infrastructure needs to be set up to be able to hold the space, for new people to come so they understand what's going on. — Nancy, Lutruwtia
-
+<!-- -->
> The work, that is primarily centered around the Netherlands, that's been going on for years, has had a local ripple effect and there are a lot of people active on this topic. We're not that well organized at the moment but there is a lot of diversity in what's going on. — crunk and d1, Rotterdam
-
+<!-- -->
> It can be a bit challenging to bring some impulses into the conversation but not take over or steer it too much. — Simon, Vienna
-
+<!-- -->
> What makes me proud is seeing people who first came to listen — then came back to present their own projects. — Brendan, Berlin
-
+<!-- -->
> Some people decided to meet in person, we are all far away from each other in Ireland, even though I, as the initiator of the group, couldn’t make it. Just seeing photos from this meet up was rewarding. — Colm, County Mayo
-
-> I feel we are proud of our consistency over time, seeing how this idea has been transformed into something concrete that has endured. We will soon celebrate 4 years of presence (in 2026), advancing at a snail's pace. Sometimes the most important thing is to hold the space. — Archipiélago I
-
+<!-- -->
+> We are proud of our consistency over time, seeing how this idea has been transformed into something concrete that has endured. We will soon celebrate 4 years of presence (in 2026), advancing at a snail's pace. Sometimes the most important thing is to hold the space. — Archipiélago I
+<!-- -->
> There's a kind of a fantasy that you can get something set up and then it'll just keep going on its own. And it just never works that way. You have to put in some effort. Just keep putting up flyers every month. — Steve, Philadelphia
-
+<!-- -->
> I'm doing that with a few, like three or four people. We are doing things very slowly so that we can have everything set up well. So when we start expanding or bringing in people, they don't go ”Oh, so let's look at their website. Oh, it's not on a green server”. I know it's a silly way to do it really, but trying to have some basics in place.[..] I say it really is like compost. If you are going to follow these principles, it will be slow computing. — Nancy, Lutruwtia
+<!-- -->
diff --git a/pour_and_share.mdwn b/pour_and_share.mdwn
@@ -1,4 +1,4 @@
-Pour and share
+Pour and Share
==============
Connect outward, share knowledge, renew the brew.
@@ -26,17 +26,18 @@ Tech, create and moderate safer spaces, or organise activist projects.
**Quotes**
> Thinking about permacomputing in other regions of the world implies recognizing the vast differences in privileges and resources. Creating and maintaining groups focused on niche topics such as permacomputing or low-tech is very different in territories that have been living in precarious conditions, under occupation, imperialism, and colonialism for centuries. — Archipiélago I
-
+<!-- -->
> If permacomputing is to be more than a blip, it’ll be because of all the people who aren’t programmers. — Brendan, Berlin
-
+<!-- -->
> The best way to heal technology is to heal ourselves. [...] Developers often understand complexity but not communication — you need both. — Michal, Prague
-
-> I think the group will form organically, without necessarily establishing it in advance. If you decide to formalize a group, try not to have hierarchies, and avoid positions of power as much as possible. Invite people who are knowledgeable about the topic to the meetings, as well as projects that may be interested in the conversation. — Archipiélago I
-
+<!-- -->
+> We think the group will form organically, without necessarily establishing it in advance. If you decide to formalize a group, try not to have hierarchies, and avoid positions of power as much as possible. Invite people who are knowledgeable about the topic to the meetings, as well as projects that may be interested in the conversation. — Archipiélago I
+<!-- -->
> In order for us to have a circular economy of computation, we need to have computational degrowth. But we cannot really do that because we don't have any notion of how to do that. All learning materials are geared towards “do it quick and use whatever materials there are.” So this is why we are looking to build alternatives. — d1 and crunk, Rotterdam
-
+<!-- -->
> I think that will be super helpful […] if you're just starting off you can just say okay I've seen that this works in another city so I can just try this out and then you don't have to be super creative on your own to come up with cool agendas for meetings but have something as a basis to build on. — Simon, Vienna
-
+<!-- -->
> Coming together and starting from there would be my advice, rather than imposing a lot of external ideals. It is really [about] starting from where people are at. What are people's computing habits? Let's talk about them! Do they name their hard drive? What do they name their hard drive and why? It's about embodied practice. For me it's very important to start with hardware [otherwise] you just [produce] e-waste. Use examples of things that people understand. — Nancy, Lutruwtia
-
+<!-- -->
> [The appeal is] also, for a lot of people, that there finally is something that isn't negative, that isn't like a critique or a “we're all doomed” story but actually something positive. — Steve, Philadelphia
+<!-- -->
