commit f13b51325bbe6732e235bc22dbb81c87596921d6
parent 32f2bc61f26ee7261ff7a2baea7d3f8c1c416873
Author: Ville-Matias Heikkila <viznut@low.fi>
Date: Fri, 15 Dec 2023 14:11:51 +0200
Merge branch 'master' of bleu255.com:/var/www/git.bleu255.com/repos/permacomputing
Diffstat:
19 files changed, 320 insertions(+), 106 deletions(-)
diff --git a/Communities.mdwn b/Communities.mdwn
@@ -1,32 +1,45 @@
Communities
===========
-This is a list of communities that may share some goals, practices or ideas with permacomputing. For ideas and ideologies that don't have communities around themselves, see [[concepts]].
+It's difficult to speak of [[Permacomputing]] as one single community. We want to welcome and include as many people as possible in the discussion.
-Practice
---------
+Discussion
+----------
+
+At the moment several groups use the following means to exchange and stay in touch with each other to discuss permacomputing and related topics:
+
+* **IRC:** #permacomputing channel on [libera.chat](https://libera.chat);
+* **XMPP:** [lowtech/permacomputing](xmpp:lowtech@chat.disroot.org?join) MUC;
+* **Email discussion list:** [permacomputing /at/ we \dot\ lurk /dot/ org](https://we.lurk.org/mailman3/lists/permacomputing.we.lurk.org/);
+* **#permacomputing**: obvious hashtag that we use on socials (mainstream and alt);
+
+Note: the IRC channel, XMPP chatroom, and the list are moderated and you must agree to our [[terms]].
+
+List of communities
+-------------------
+
+The following includes communities that may share some goals, practices or ideas with permacomputing. For ideas and ideologies that don't have communities around themselves, see [[concepts]].
+
+**Practical**:
* [[Appropriate technology]]
* [[Collapse computing]]
* [[FLOSS]]
- * [[Gemini]]
* [[Smallnet]]
+ * See also: [[projects]]
-Academic
---------
+**Academic**:
* [[Computing within Limits]]
* [[Sustainable ICT]]
-Activism, Policy Making and Legislation
-----------------------------------------
+**Activism, Policy Making and Legislation**:
* [[offline first]]
* [[right to repair]]
* [[Green software engineering]]
-Artistic
---------
+**Artistic**:
* [[Small File Media Festival]]
* [[Algorave]]
diff --git a/TODO.mdwn b/TODO.mdwn
@@ -18,9 +18,7 @@ ikiwiki
Content
-------
-* New editing guide from Ola/giz
* section for curriculum postdoc thing (wip)
* section on workshop outline "The Cloud is Just My Old Computer"
-* new landing page structure from katía/crunk
-* list of all the ppl contributing
+* new landing page structure from katía/crunk (wip)
* laypeople-accessible introduction to permacomputing
diff --git a/about.mdwn b/about.mdwn
@@ -1,13 +1,13 @@
-About
-=====
-
This website is a [[wiki]] dedicated to [[permacomputing]].
+Contact us!
+-----------
+
+The Permacomputing wiki is facilitated by [[ugrnm]] and [[viznut]]. Its content is written by (in order of registration): [[neau]], [[thgie]], [[akkartik]], [[aw]], [[orx]], [[dusan]], [[katía]], [[luen]], [[suj]], [[cmos4040]], [[giz]], [[pixouls]], [[wakame]], [[decentral1se]], [[clwil]]
-Contributing
-------------
+You can reach all of us at once by sending an email to:
-If you want to contribute to the permacomputing wiki, read the page about [[editing]].
+ **permacomputing / a t / bleu255 \ dot \ c o m**
HTTP vs HTTPS
diff --git a/contact.mdwn b/contact.mdwn
@@ -3,6 +3,26 @@ The Permacomputing wiki is facilitated by:
* [[ugrnm]]
* [[viznut]]
-There currently a dozen editors (FIXME: LIST!), you can reach us all at **permacomputing / a t / bleu255 \ dot \ c o m**
+Its content is written by (in order of registration)
+
+* [[neau]]
+* [[thgie]]
+* [[akkartik]]
+* [[aw]]
+* [[orx]]
+* [[dusan]]
+* [[katía]]
+* [[luen]]
+* [[suj]]
+* [[cmos4040]]
+* [[giz]]
+* [[pixouls]]
+* [[wakame]]
+* [[decentral1se]]
+* [[clwil]]
+
+You can reach all of us at once by sending an email to **permacomputing / a t / bleu255 \ dot \ c o m**
+
+Do you want to contribute something? Great, check [[this page|editing]]!
diff --git a/contribute.md b/contribute.md
@@ -0,0 +1,19 @@
+Access
+------
+
+If you feel like you belong here, you are very welcome to contribute to this wiki!
+
+**IMPORTANT: let's not have any misunderstanding. Permacomputing is a political project. It is driven by several strands of anarchism, feminism, post-marxism, degrowth, environmentalism. We're not here to help you greenwash your new sustainable ICT ideas, green AI, innovative art+science projects, ecological web3 funding, and other nonsensical technosolutionist forms of climate denial. Please go elsewhere :)**
+
+You can [[contact|about]] us by email for an account. Please:
+
+* Present yourself briefly;
+* Include URLs to work/project/socials/etc;
+* Explain your interest in permacomputing and tell us what/why/how you would
+like to contribute to the wiki;
+* Confirm that you have read the [[editing guideline|editing]] and agree to our
+[[terms]].
+
+Please cover these four points, we won't process/reply vague or incomplete
+requests. Really, we won't. It may take a few days for us to get back to you.
+
diff --git a/editing.mdwn b/editing.mdwn
@@ -1,38 +1,82 @@
-Access
-======
+Style
+-----
-You are very welcome to contribute to this wiki!
+Permacomputing wiki is not [[Wikipedia]], so being neutral or encyclopedic is
+not among our goals, and original research is encouraged. However, it is a
+collaborative project, so if you want to express an opinion the other editors
+may not agree with, please use the relevant Discussion page, and make sure to
+sign your comment with your handle. Go to the Discussion page, in the top menu
+of this page for an example.
-You can [[contact]] us by email for an account. Please:
-* Present yourself briefly;
-* Include URLs to work/project/socials/etc;
-* Explain your interest in permacomputing and tell us what/why/how you would like to contribute to the wiki;
-* Confirm that you have read the editing guideline (this page) and agree to our [[terms]].
+Copyediting recommendations
+---------------------------
-Please cover these four points, we won't process/reply vague or incomplete requests. It may take a few days for us to get back to you.
+1. explain the abbreviations before using it (ex. Operations Systems (OS) are
+ amazing. The OS are actually shit).
-What belongs on this wiki?
---------------------------
+2. make sure the references are explained before using them. (ex. "Unix is a
+ multi-user operating system whose development was started in 1969 by Ken
+ Thompson and Dennis Ritchie, as well as an entire family of operating system
+ derived from the original Unix." First, explain the original Unix, or
+ rearrange the sentences where you explain what unix is, then explain that
+ there are multiple versions, an original and others). Same for people
+mentioned, quotes, etc.
-Basically any topic is allowed as long as it can be discussed from a permacomputing-relevant point of view. For an outline of the kind of topics we are particularly interested in, see the front page.
+3. explain the relevance of a quote.
+4. transition between paragraphs, quotes etc. is key. similar to the rule
+ above, make sure the paragraphs are transitioning from one point to another.
-Style
-=====
+5. avoid jargon. if a technical/academic/etc term needs to be used, maybe it
+ needs its own page as well. (i.e. "it refers to a very specific kind of
+ 'digital', a highly technoprogressivist and industry-defined kind that
+ became prominent in the 'digital revolution' hype of the 1990s."
+ technoprogressivist is not a common word that could be understood easily,
+ either provide a short explanation or make a page for it)
+
+6. check if there are other pages you can crosslink in your text (i.e. you
+ mention hardware, link the hardware page there)
+
+7. avoid using brackets (as much as possible), it breaks the reading (and
+ comprehending) flow (quite a bit) (right?).
+
+8. avoid passive-aggresive language. rather, explain why some concepts are
+ wrong/didn't work/are bad. (i.e. "digital revolution" hype of the 1990s. why
+ was it a hype?)
-Permacomputing wiki is not [[Wikipedia]], so being neutral or encyclopedic is not among our goals, and original research is encouraged. However, it is a collaborative project, so if you want to express an opinion the other editors may not agree with, please use the relevant Discussion page, and make sure to sign your comment with your handle. Go to the Discussion page, in the top menu of this page for an example.
+9. make sure all formatting choices are unified in your text. (i.e.
+ https://permacomputing.net/Principles/ here, the sub-principles are written
+ as a paragraph first, and then as list. should be the same style).
-At the current stage of maturity of PW, it is often not advisable to write a comprehensive articles about a topic if someone else has already done it elsewhere. Put in a link to that external resource instead. (In the future, we will perhaps want to host copies of all these "dependencies" in the local repository as well, but not yet.)
+10. use formatting sparingly and with purpose.
-When introducing a new term, please try to include a proper and non-biased definition of the topic before proceeding to the permacomputing-specific points of view. You can use [[Wikipedia]] or other sources for this, **just make sure you properly attribute and quote** (we are CC0, Wikipedia is CC-BY-SA, so you can't just copy-and-paste even from there). See below.
+11. avoid repetation and redundant words, be concise, simple, clear.
+12. don't forget to save! :D
-Attribution, quotes and footnotes
----------------------------------
-If you rely on other sources for the writing of a section, do not be lazy or mindlessly copypaste from other sources. In general, **do not invisibilize people from which you took inspiration and/or learned something from**. Take the opportunity of contributing to this wiki to also point to their work and research. You must properly attribute your source. You have 4 options:
+On attribution, quotes and footnotes
+------------------------------------
+
+At the current stage of maturity of this wiki, it is often not advisable to
+write a comprehensive articles about a topic if someone else has already done
+it elsewhere. Put in a link to that external resource instead. (In the future,
+we will perhaps want to host copies of all these "dependencies" in the local
+repository as well, but not yet.)
+
+When introducing a new term, please try to include a proper and non-biased
+definition of the topic before proceeding to the permacomputing-specific points
+of view. You can use [[Wikipedia]] or other sources for this, **just make sure
+you properly attribute and quote** (we are CC0, Wikipedia is CC-BY-SA, so you
+can't just copy-and-paste even from there).
+
+If you rely on other sources for the writing of a section, do not be lazy or
+mindlessly copypaste from other sources. In general, **do not invisibilize
+people from which you took inspiration and/or learned something from**. Take
+the opportunity of contributing to this wiki to also point to their work and
+research. You must properly attribute your source. You have 4 options:
* **Hyperlinks:** Sometimes it's enough to point to external reference as an hyperlink if there is not much to discuss. For instance [Ursula K. Le Guin has an interesting take on technology](http://www.ursulakleguinarchive.com/Note-Technology.html).
* **Footnotes:** Can be handy to drift a bit[^drift] but also to give a proper footnote reference when paraphrasing and referencing the thoughts of someone else. For instance Ursula K. Le Guin has been critical of a specific usage of the work *technology* when misused to only refer to the most recent developments, which also happen to be the most problematic[^leguinref].
@@ -49,25 +93,37 @@ If you rely on other sources for the writing of a section, do not be lazy or min
[^leguinrefquote2]: Ursula K. Le Guin, "A Rant About 'Technology'," 2004, [http://www.ursulakleguinarchive.com/Note-Technology.html](http://www.ursulakleguinarchive.com/Note-Technology.html).
-Limitations of the footnotes
-----------------------------
+### Limitations of the footnotes
-This it not biblatex/biber. So as you can see in the examples above, you cannot reuse an existing footnote, and there is not elegant handling of repetition (no Ibid.).
+This it not biblatex/biber. So as you can see in the examples above, you cannot
+reuse an existing footnote, and there is not elegant handling of repetition (no
+Ibid.).
Reference style
---------------
-When referencing, please use the [Notes and Bibliography version of The Chicago Manual of Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). However, this is not an academic paper, don't overthink it or spend ages on it, try to make it work as best as you can, it's just to have some overall consistency. No sweat :)
+When referencing, please use the [Notes and Bibliography version of The Chicago
+Manual of
+Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html).
+However, this is not an academic paper, don't overthink it or spend ages on it,
+try to make it work as best as you can, it's just to have some overall
+consistency. No sweat :)
Acceptable content
-==================
+------------------
-While it is obvious that it is expected that your contribution relate to the topics and themes of permacomputing, you agree that your content does not break the [[terms]] of the permacomputing community.
+Basically any topic is allowed as long as it can be discussed from a
+permacomputing-relevant point of view and do not break the [[terms]].
Licensing
-=========
-
-While editing the Permacomputing wiki, you agree that your contribution will be published and made available under the [CC0 Waiver](https://creativecommons.org/publicdomain/zero/1.0/legalcode-plain). If you use images, photos, from other sources, please make sure to give full credit and if available the license/tersm under which the image is made available.
+---------
+
+While editing the Permacomputing wiki, you agree that your contribution will be
+published and made available under the [CC0
+Waiver](https://creativecommons.org/publicdomain/zero/1.0/legalcode-plain). If
+you use images, photos, from other sources, please make sure to give full
+credit and if available the license/tersm under which the image is made
+available.
diff --git a/events.mdwn b/events.mdwn
@@ -1,11 +1,52 @@
-Events
+#Events
------
-* 2023/09/21 - [Permacomputing Talk](https://thestrangeloop.com/2023/an-approach-to-computing-and-sustainability-inspired-from-permaculture.html), Strange Loop 2023
-* 2023/09/20 - Permacomputing Meetup, Saint-Louis, Missouri
-* 2022 - Permacomputing overview as part of [[What Remains]] presentation, Natural Intelligence Lab, FIBER, Amsterdam.
-* 2022/06/26 - [Permacomputing meetup](https://iffybooks.net/event/permacomputing-meetup-june/) at Iffy Books, Philly.
-* 2023/06/24 - [Gardening as Electricity Making](https://varia.zone/en/gardening-as-electricity-making.html) at Varia, Rotterdam.
-* 2023/01/23 - [Permacomputing meetup](https://iffybooks.net/event/permacomputing-january/) at Iffy Books in Philadelphia, PA, USA
+This section features workshops, talks, and other permacomputing connected activities. If you are planning to organize your own event and want to be featured or would like to link an existing permacomputing activity, please [[contact]] us!
+
+##Upcoming
+### 2023/12/02 [Practices of Digital Resilience & Permacomputing](https://www.fiber-space.nl/permacomputingsymposium/)
+In collaboration with Fiber, some active members of the permacomputing community, and the Unsustainable Research Group of the Willem de Kooning Academy, welcomes you to a day full of talks at Tolhuistuin, where a lineup of speakers will offer different perspectives on translating sustainability, resilience, and regeneration principles into practical steps.
+
+### 2023/11/30 - 2023/12/01 - [Workshop] by [Brendand Howell](https://monoskop.org/Brendan_Howell) & [Michal Klonder](https://livinglab.node9.org/) Networking with Nature: Connecting plants and second-hand electronics, Fiber Reassemble Lab 2023
+
+>**[In this 2 day workshop](https://www.fiber-space.nl/networking-with-nature/)**, participants will collaborate to build a small cybernetic system integrating plants, humans and electronics. We will begin with a few simple experiments with analog forms of networks and some investigations into the kinds of media we can use to convey with plants. With our results, we will then continue to construct a small, sustainable “network of care” – a living laboratory of sorts using second-hand electronics and our low-powered micro-server.
+
+
+
+
+### 2023/11/17 - 2023/11/18 - [Workshop] by [Ola Bonati](https://olabonati.com/) Imagination above Productivity | Resurfacing and scaling the digital ecosystem around us, Fiber Reassemble Lab 2023
+
+>**[In this 2-day workshop](https://www.fiber-space.nl/imagination-above-productivity-resurfacing-and-scaling-the-digital-ecosystem-around-us/)** we will shed, share, and explore new tools and methods for fostering collective imagination beyond productivity quotas. Participants will be asked to collaborate in smaller teams on one of the emergent themes. The workshop outcomes will be presented and published at the end of the workshop series.
+
+
+##Past
+
+### 2023/10/13 - 2023/10/14/ - [Workshop] by [Aymeric Mansoux](https://bleu255.com/~aymeric/) & [Lukas Engelhardt](https://lukasengelhardt.net/) The Cloud is Just my Old Computer | Creating a permacomputing server, Fiber Reassemble Lab 2023
+
+>**[In this 2-day workshop](https://www.fiber-space.nl/the-cloud-is-just-my-old-computer/)** hosted in collaboration with Fiber, participants learned how to turn their old hardware into a functional server that can be used to host a website or some useful web applications for yourself, friends, family, or colleagues. The idea was to give participants enough knowledge to continue exploring this alternative cloud by themselves.
+
+### 2023/09/21 - [Talk] [Devine Lu Linvega](https://wiki.xxiivv.com/site/home.html), An Approach To Computing and Sustainability Inspired From Permaculture, Strange Loop 2023
+
+>"Devine Lu Linvega is a designer and musician living aboard a sailboat somewhere on the foggy shores of the Pacific Ocean. Devine has been developing and teaching livecoding environments all the while fending off the rising tide of noxious modern software and operating systems."
+
+ **[watch the talk here](https://www.youtube.com/watch?v=T3u7bGgVspM&ab_channel=StrangeLoopConference)**
+
+### 2023/09/20 - [Meetup] Permacomputing Meetup, Saint-Louis, Missouri
+
+### 2022/10/28 [Talk] Introduction to Permacomputing, [Zine Camp in Rotterdam](https://zinecamp2022.hotglue.me/)
+
+The presentation by Aymeric Mansoux and Ola Bonati explained the basics of permacomputing, its principles, and the relevance of this concept to the practice of self-publishing. During the event, we played an interactive session of permacomputing bingo (crappy tech bingo) originally sourced from the answers given by the members PMC wiki mailing list.
+Thanks again to everyone who contributed to the list of tech miseries!
+
+
+### 2022/03/10 - [Talk] Permacomputing overview as part of [Natural Intelligence Lab] presentation, FIBER, Amsterdam.
+
+
+**[watch it here](https://www.youtube.com/live/OOppK1or6RY?si=p1ufbciwC8PK6sJa)**
+
+
+### 2022/06/26 - [Meetup] Permacomputing meetup (https://iffybooks.net/event/permacomputing-meetup-june/) at Iffy Books, Philly.
+### 2023/06/24 - [Meetup] [Gardening as Electricity Making](https://varia.zone/en/gardening-as-electricity-making.html) at Varia, Rotterdam.
+### 2023/01/23 - [Permacomputing meetup](https://iffybooks.net/event/permacomputing-january/) at Iffy Books in Philadelphia, PA, USA
TODO: lots of stuff missing: edit-a-thon, LIMITS, ETHO/ELIA, pmc photo, Critical Infra lab launch, RHUL seminar, Zinecamp, etc.
diff --git a/everything.mdwn b/everything.mdwn
@@ -0,0 +1 @@
+[[!map pages="*"]]
diff --git a/everything2.mdwn b/everything2.mdwn
@@ -0,0 +1 @@
+[[!pagestats style="table" pages="*"]]
diff --git a/getting_started.mdwn b/getting_started.mdwn
@@ -0,0 +1,90 @@
+How to get started? Watdo? Wydo?
+--------------------------------
+
+This is a frequent question, and not an easy one to answer, but here are some
+suggestions:
+
+* **Branching**: Permacomputing can take many forms. Contexts and situations
+are different. For someone it may be about writing their own FORTH for a chip
+reclaimed from e-waste; for someone else it may be about helping artists
+interested to engage with ecological topics using tools and media in line with
+this intention; for a family it could be about discussing the use/impact of
+smartphones in the household; for another it could be about helping a school
+working with recycled computers; for another it could be about researching how
+to provide less resource intensive tools and systems for their lab; for yet
+another person it may be about engaging with politics and policy making to
+advance tech and enviro regulation in their own institution, town, region, etc.
+Of course overlaps and interleaving in such branching can be very useful!
+
+* **Experimenting**: Do you need to buy it? Could you repurpose an old computer
+or device instead? If you're going to develop something new, what are you gonna
+use to ensure you make something that does not end up being harmful or
+wasteful? Does it need to be a computer anyway? Do you need to acquire new
+skills? How will you acquire these skills? Can you afford to learn such skills?
+Could you figure it out with the help of others? With computation and computer
+tech consumerism taking such a big space in so many activities, it is very
+likely that a domain, a common/everyday tool, a practice, in which you have
+interest, professionally or not, could become your field of experimentation.
+
+* **Publishing**: Regardless what you do, it will be very inspiring to others
+if you document it a bit. Successes *and* failures. It does not have to be
+extensive, but it can be a much more effective way to demonstrate how to
+activate critical practices in relation to computer tech. You can do that on
+your own website if you have one, you can make zines, something individual or
+something with others, and of course you could use this wiki! More generally
+publishing does not need to be only about the projects you are involved with
+directly, maybe it is about helping others writing a manual, a cookbook, a
+sampler, something relatable and accessible.
+
+* **Participating**: Some permacomputing activities can make sense as
+individual practices or be related to lifestyle choices and experiments, but
+this is only one aspect. Another equally important point of leverage is to
+discuss these things within your institution, union, building, company, town
+council, to collectively, and also infrastructurally, figure out new ways to
+discus the impact, regulation or guide the usage and re-use of computers. Join
+a union, join an environmentalist group, join a citizen science lab, etc. It's
+also important that users of hardware and software feel confident enough to
+voice their opinion, specially when the development of these projects is done
+in a relatively open way. For instance, issue trackers can be important
+activation sites to voice struggles beyond reporting technical faults.
+
+* **Organizing**: Consider starting a local group around permacomputing. You
+don't have and should not try to work on this topic on your own! Talk to local
+cultural organisations, hackerspaces, squats, town councils, schools and
+universities to help organising some events, workshops, skill-sharing sessions,
+show&tell, etc. Try to bootstrap a small permacomputing community. Make use of
+our [[code of conduct|terms]] to get you started with questions of moderation,
+make use of the wiki, communicate on the existing lists, chats, or start your
+own!
+
+* **Reading/learning**: The question of literacy in relation to computational
+culture is often reduced to staying in the loop with the latest development of
+the ICT industry and acquiring technological skills. Of course if someone who
+is not a programmer or frequent user of computers want to dive into
+permacomputing related practices, some minimal knowledge and jargon could help
+a lot. But we rarely talk about the other way around. A lot of the radical
+thinking in computer science, software and hardware engineering, seems to be
+too often stuck on the same old 60-70s US countercultural ideas. We think that
+it's important that people with a strong technological background start to
+catch up with decades of the various strands of computational critique
+discussed in feminist studies, gender studies, software studies, cultural
+studies, and also arts and humanities.
+
+Finally, and most importantly:
+
+* **Breaking the monoculture**: Like any other community of practice that
+emerged from contemporary computer tech circles, permacomputing suffers from
+very poor cultural diversity. How can we make this space more accessible and
+inclusive? Like, really. Not just empty words. How can the privileges that some
+of us have to be able to dedicate time on such topics can be generative of
+activities that can contribute to breaking the tech monoculture and how can the
+permacomputing space, including this wiki, can become a platform for less
+privileged groups to be represented *and* supported?
+
+
+
+
+Note: the first version of this document was motivated by, and in part inspired
+from, discussions and contributions from participants of the LIMITS 2023
+workshop. THANKS <3
+
diff --git a/help.mdwn b/help.mdwn
@@ -1,26 +0,0 @@
-How to Help? Watdo? Wydo?
---------------------------
-
-This is a frequent question, and not an easy one to answer, but here are some suggestions:
-
-* Branching: Permacomputing can take many forms. Contexts and situations are different. For someone it may be about writing their own FORTH for a chip reclaimed from e-waste; for someone else it may be about helping artists interested to engage with ecological topics using tools and media in line with this intention; for a family it could be about discussing the use/impact of smartphones in the household; for another it could be about helping a school working with recycled computers; for another it could be about researching how to provide less resource intensive tools and systems for their lab; for yet another person it may be about engaging with politics and policy making to advance tech and enviro regulation in their own institution, town, region, etc. Of course overlaps and interleaving in such branching can be very useful!
-
-* Experimenting: Do you need to buy it? Could you repurpose an old computer or device instead? If you're going to develop something new, what are you gonna use to ensure you make something that does not end up being harmful or wasteful? Does it need to be a computer anyway? Do you need to acquire new skills? How will you acquire these skills? Can you afford to learn such skills? Could you figure it out with the help of others? With computation and computer tech consumerism taking such a big space in so many activities, it is very likely that a domain, a common/everyday tool, a practice, in which you have interest, professionally or not, could become your field of experimentation.
-
-* Publishing: Regardless what you do, it will be very inspiring to others if you document it a bit. Successes *and* failures. It does not have to be extensive, but it can be a much more effective way to demonstrate how to activate critical practices in relation to computer tech. You can do that on your own website if you have one, you can make zines, something individual or something with others, and of course you could use this wiki! More generally publishing does not need to be only about the projects you are involved with directly, maybe it is about helping others writing a manual, a cookbook, a sampler, something relatable and accessible.
-
-* Participating: Some permacomputing activities can make sense as individual practices or be related to lifestyle choices and experiments, but this is only one aspect. Another equally important point of leverage is to discuss these things within your institution, union, building, company, town council, to collectively, and also infrastructurally, figure out new ways to discus the impact, regulation or guide the usage and re-use of computers. Join a union, join an environmentalist group, join a citizen science lab, etc. It's also important that users of hardware and software feel confident enough to voice their opinion, specially when the development of these projects is done in a relatively open way. For instance, issue trackers can be important activation sites to voice struggles beyond reporting technical faults.
-
-* Organizing: Consider starting a local group around permacomputing. You don't have and should not try to work on this topic on your own! Talk to local cultural organisations, hackerspaces, squats, town councils, schools and universities to help organising some events, workshops, skill-sharing sessions, show&tell, etc. Try to bootstrap a small permacomputing community. Make use of our [[code of conduct|terms]] to get you started with questions of moderation, make use of the wiki, communicate on the existing lists, chats, or start your own!
-
-* Reading/learning: The question of literacy in relation to computational culture is often reduced to staying in the loop with the latest development of the ICT industry and acquiring technological skills. Of course if someone who is not a programmer or frequent user of computers want to dive into permacomputing related practices, some minimal knowledge and jargon could help a lot. But we rarely talk about the other way around. A lot of the radical thinking in computer science, software and hardware engineering, seems to be too often stuck on the same old 60-70s US countercultural ideas. We think that it's important that people with a strong technological background start to catch up with decades of the various strands of computational critique discussed in feminist studies, gender studies, software studies, cultural studies, and also arts and humanities.
-
-Finally, and most importantly:
-
-* Breaking the monoculture: Like any other community of practice that emerged from contemporary computer tech circles, permacomputing suffers from very poor cultural diversity. How can we make this space more accessible and inclusive? Like, really. Not just empty words. How can the privileges that some of us have to be able to dedicate time on such topics can be generative of activities that can contribute to breaking the tech monoculture and how can the permacomputing space, including this wiki, can become a platform for less privileged groups to be represented *and* supported?
-
-
-
-
-Note: the first version of this document was motivated by, and in part inspired from, discussions and contributions from participants of the LIMITS 2023 workshop. THANKS <3
-
diff --git a/index.mdwn b/index.mdwn
@@ -9,7 +9,7 @@ In a time where computing epitomizes industrial waste, permacomputing encourages
If you want to know more, please start reading about what is [[permacomputing]] in essence, and then dive into its [[principles]].
-If you want to help, [[here are some suggestions|help]].
+If you want to help, [[here are some suggestions|getting_started]].
Wiki
@@ -17,7 +17,7 @@ Wiki
Started in May 2022, the permacomputing [[wiki]] is where we maintain a set of principles, collectively document practical perspectives and interpretations of these principles, and offer more speculative reflections on permacomputing.
-**The wiki is still at a very early stage of development, we are frequently working on it.**
+**The wiki is still at a very early stage of development,we are frequently working on it.**
This main page of the wiki is an index to the various topics covered. See "[[about]]" for a more detailed discussion about the wiki itself.
@@ -36,29 +36,28 @@ Theory
Practice
--------
-
+* [[Events]] Learn more about current and upcoming activities!
* [[Projects]] that (may) have some permacomputing relevance;
* [[Assessments]] of existing and established pieces of technology;
* [[Hardware]] information;
* [[Courses and workshops]];
-* [[permacomputing-cookbook]].
Around, nearby and beyond
-------------------------
* [[Communities]] that (may) have compatible goals and interests;
* More fine-grained [[properties]] of software built using permacomputing principles, and how they're shared by neighboring communities;
-* [[Damaged Earth Catalog]] covers concepts and movements related to permacomputing.
+* [[Damaged Earth Catalog|DEC]] covers concepts and movements related to permacomputing.
Community?
==========
-It's difficult to speak of [[Permacomputing]] as a community just yet. However we would like to welcome and include as many people as possible in the discussion. At the moment several groups use the following means to exchange and stay in touch with each others to discuss about permacomputing and related topics:
+It's difficult to speak of [[Permacomputing]] as one single community. We want to welcome and include as many people as possible in the discussion. At the moment several groups use the following means to exchange and stay in touch with each other to discuss permacomputing and related topics:
* **IRC:** #permacomputing channel on [libera.chat](https://libera.chat);
* **XMPP:** [lowtech/permacomputing](xmpp:lowtech@chat.disroot.org?join) MUC;
* **Email discussion list:** [permacomputing /at/ we \dot\ lurk /dot/ org](https://we.lurk.org/mailman3/lists/permacomputing.we.lurk.org/);
* **#permacomputing**: obvious hashtag that we use on socials (mainstream and alt);
-* [[Events]] about permacomputing.
-Note: the IRC channel and the list are moderated and you must agree to our [[terms]].
+
+Note: the IRC channel, XMPP chatroom, and the list are moderated and you must agree to our [[terms]].
diff --git a/index3.mdwn b/index3.mdwn
@@ -2,9 +2,6 @@ Welcome to the Permacomputing wiki!
-What?
------
-
**[[Permacomputing]]** is both a concept and a community of practice
oriented around issues of resilience and regenerativity in computer and
network technology inspired by permaculture.
@@ -24,11 +21,11 @@ For more information:
* [[Issues]] in today's computing
* [[Wiki]] information
-How?
-----
+Resources:
-* [[Starter's manual]]
+* [[Starter's manual|getting_started]]
* [[Projects]]
* [[Communities]] of Practice
* [[Courses and workshops]]
* [[Library]]
+* [[Contribute to the wiki|contribute]]
diff --git a/library.mdwn b/library.mdwn
@@ -1,6 +1,8 @@
Library
=======
+this.is.a.work.in.progress :)
+
Texts
-----
diff --git a/local.css b/local.css
@@ -36,7 +36,7 @@ body {
}
h1,h2,h3,h4,h5,h6 {
font-family: sans-serif;
- letter-spacing: -2px;
+ letter-spacing: 0.5px;
}
h1 {
margin-bottom: 0em;
diff --git a/ola.mdwn b/ola.mdwn
@@ -0,0 +1 @@
+dfgrdrgf
diff --git a/orphans.mdwn b/orphans.mdwn
@@ -0,0 +1,3 @@
+Send help :)
+
+[[!orphans pages="*"]]
diff --git a/permacomputing-cookbook.mdwn b/permacomputing-cookbook.mdwn
@@ -1,5 +1,8 @@
## a cookbook for permacomputing ##
+**!Nov.23: The project was discontinued due to insufficient resources and cooperation.**
+
+. . . .
Bringing the idea of permacomputing to a broader audience would ideally use a "down-to-earth"-HowTo. This subproject aims to design and publish a "Cookbook for Permacomuting" that lists easy achievable concepts and guidelines for action in project form.
Goals of the the book are:
@@ -24,21 +27,17 @@ This is a relatively young project, having started in May 2023. Currently, two m
2) **Acquiring financial support**: We are currently searching the political map, that means above all the European and German Greens, for foundations or funding pots that would support such a cookbook. The amount of money would have to be about € 12K to support a small, part-time editorial team for about a year, who can take care of content, such as written contributions or pictures and graphics.
-[Read here the first draft](https://arbeitsgruppen.clauswilcke.de/lib/exe/fetch.php?media=application-foundation-funds_cookbook-permacomputing.pdf/ "Application of foundation funds for the production of a
-'Cookbook for Permacomputing'") of the Application of foundation funds for the production of a
-“Cookbook for Permacomputing"
-
-### Participation welcome: ###
-We welcome anyone and everyone who wants to take part in this and would be very happy to have any help in driving this project forward. The first milestone is autumn 2023, when the first version of the cookbook will be available as a downloadable PDF on this wiki.
- Claus info [at} clauswilcke [dot} com
## what has happened so far: ##
+### November '32###
+*The project was discontinued due to insufficient resources and cooperation
+
### July '23 ###
* Setting up this page
* [ first draft draft](https://arbeitsgruppen.clauswilcke.de/lib/exe/fetch.php?media=application-foundation-funds_cookbook-permacomputing.pdf/ "Application of foundation funds for the production of a 'Cookbook for Permacomputing'") for a application of funding
-### June '23 __ ###
+### June '23 ###
* Contacting the European Greens in search of financial support/foundations
* Contacting the Greens in the German Bundestag in search of financial support/foundations
diff --git a/templates/page.tmpl b/templates/page.tmpl
@@ -192,7 +192,7 @@ Links:
</TMPL_IF>
<div class="bottom_menu">
-<a href="<TMPL_VAR BASEURL>about/">About</a> | <a href="<TMPL_VAR BASEURL>contact/">Contact</a> | <a href="<TMPL_VAR BASEURL>license/">LICENSE</a> | <span class="last_edit">Last edit <TMPL_VAR MTIME></span>
+<a href="<TMPL_VAR BASEURL>about/">About</a> | <a href="<TMPL_VAR BASEURL>contribute/">Contribute to the wiki</a> | <a href="<TMPL_VAR BASEURL>license/">LICENSE</a> | <a href="<TMPL_VAR BASEURL>terms/">Terms</a> | <span class="last_edit">Last edit <TMPL_VAR MTIME></span>
<!-- Created <TMPL_VAR CTIME> -->
</div>
