commit bc279b7109ae76c8f2894d0953ddccf1951f5b73
parent 659a25b5fdf7c1172ae82cb3f32a54a72ffaec0f
Author: ugrnm <ultrageranium@bleu255.com>
Date: Fri, 6 Jun 2025 12:36:07 +0200
principles sub pages
Diffstat:
| M | principles2.mdwn | | | 463 | +++++++++++++++++++++++++++++++++++++++++-------------------------------------- |
1 file changed, 239 insertions(+), 224 deletions(-)
diff --git a/principles2.mdwn b/principles2.mdwn
@@ -1,12 +1,20 @@
-## Exploring the Permacomputing Principles ~
+Introduction
+------------
-**Introduction**
+Contemporary permaculture is founded on three core ethics: Earth Care, People
+Care, and Fair Share. These ethics serve as a guiding compass for its design
+principles, co-creating a holistic framework for regenerative living.
+Similarly, permacomputing is built upon 10 principles that encourage and raise
+awareness about more sustainable digital practices.
-Contemporary permaculture is founded on three core ethics: Earth Care, People Care, and Fair Share. These ethics serve as a guiding compass for its design principles, co-creating a holistic framework for regenerative living. Similarly, permacomputing is built upon 10 principles that encourage and raise awareness about more sustainable digital practices.
+Whether you are a tech specialist, someone who uses computer for daily tasks or
+only occasionally, there are steps that individuals and groups can take to
+reduce the environmental and socio-economic impact of their digital activities.
+The following section explores the permacomputing principles, each illustrated
+through:
-Whether you are a tech specialist, someone who uses computer for daily tasks or only occasionally, there are steps that individuals and groups can take to reduce the environmental and socio-economic impact of their digital activities. The following section explores the permacomputing principles, each illustrated through:
-
-On this page, you can explore permacomputing principles, each illustrated through:
+On this page, you can explore permacomputing principles, each illustrated
+through:
- **Urgency/background**
- **What can YOU do?**
@@ -15,294 +23,301 @@ Strategies and interventions for all, from techie to casual user, or something i
Further reading, tools for deeper engagement, and examples of implementation
-The community of permacomputing promotes a comprehensive approach to the design of human technology, taking into account social and ecological issues, encouraging resilience and supporting a fair coexistence.
-These design principles are not just technical guidelines but represent strategies for positive changes.
-
-That said, permacomputing is not prescriptive; it instead favors situatedness and an awareness of contextual diversity.
-We, the Permacomputing working group, hope these design principles can serve both as a guide for practice in specific situations and as a tool for identifying systemic issues in the relationship between computer technology and ecology.
-
+The community of permacomputing promotes a comprehensive approach to the design
+of human technology, taking into account social and ecological issues,
+encouraging resilience and supporting a fair coexistence. These design
+principles are not just technical guidelines but represent strategies for
+positive changes.
-Furthermore, the Permacomputing community is more than this site!
-It is inspired by—and builds upon—a diverse range of initiatives, research, projects, and bodies of knowledge.
+That said, permacomputing is not prescriptive; it instead favors situatedness
+and an awareness of contextual diversity. We, the Permacomputing working group,
+hope these design principles can serve both as a guide for practice in specific
+situations and as a tool for identifying systemic issues in the relationship
+between computer technology and ecology.
-These principles are intended to be continually developed and refined.
-The text below is meant to serve as a starting point. :)
----
-## Hope for the Best, Prepare for the Worst
-It is good practice to design systems that are resilient and tolerant to interruptions and even if you do not personally believe such scenarios are imminent. This principle invites reflection: **why prioritize resilience? Rather than being a defeatist mindset, it is a practical exercise. **
+Furthermore, the Permacomputing community is more than this site! It is
+inspired by—and builds upon—a diverse range of initiatives, research, projects,
+and bodies of knowledge.
-By imagining a world shaped by scarcity, you sharpen your creativity and adaptability. Acknowledging breakages happen and taking into account the possibility of collapse can inspire self-imposed limitations that lead to resourceful solutions—often uncovering societal scenarios previously unexplored, while also acknowledging that less privileged groups are already experiencing harm and damage.
+These principles are intended to be continually developed and refined. The text
+below is meant to serve as a starting point. :)
-[[do you want to know more|hope for the best prepare for the worst]]
---
-## Care for All Hardware — Especially the Chips
-Caring for the planet also means caring for the material foundations of digital technology: our hardware. Every device, chip, and component originates from Earth’s finite resources—and eventually end up as e-waste.
+Hope for the Best, Prepare for the Worst
+----------------------------------------
-The production of new hardware—especially microchips, which are at the heart of nearly every device we use, is highly resource-intensive and energy-consuming. Microchips are particularly problematic because they are difficult to recycle, cost an immense amount of energy and resources to manufacture and their production is highly polluting. Maximizing the lifespan of hardware components is critical for reducing environmental impact and promoting a more sustainable and less harmful digital culture.
+It is good practice to design systems that are resilient and tolerant to
+interruptions and even if you do not personally believe such scenarios are
+imminent. This principle invites reflection: **why prioritize resilience?
+Rather than being a defeatist mindset, it is a practical exercise. **
-One of the core principles of permaculture is to "produce no waste," encouraging us to value and reuse all resources at hand, turning waste into a resource whenever possible.
-
-Digital technology cannot be produced without waste. To mitigate this situation, this principle calls us to step outside the capitalist model of perpetual consumption and growth. Instead, it invites us to recognize the inherent value of the devices, components, and materials we already have—and to care for them intentionally. Caring for the planet also means caring for the material foundations of digital technology: our hardware.
-**Every chip and component is made from Earth’s finite resources, and once discarded, becomes part of the growing e-waste crisis.**
-By acknowledging that these devices are not self-sustaining, we underscore the importance of extending their lifespan through intentional maintenance and thoughtful use.
+By imagining a world shaped by scarcity, you sharpen your creativity and adaptability. Acknowledging breakages happen and taking into account the possibility of collapse can inspire self-imposed limitations that lead to resourceful solutions—often uncovering societal scenarios previously unexplored, while also acknowledging that less privileged groups are already experiencing harm and damage.
-What can you do?
+[[do you want to know more|hope for the best prepare for the worst]]
-With or without a computer:
-- Value what you have. Treat your hardware with care, appreciating its quirks and limitations.
-- Repair what can be repaired. Timely maintenance prevents greater damage and extends your device’s life.
-- Think before you buy. Ask yourself whether a new purchase is truly necessary, or if existing tools could meet your needs more sustainably.
-- Support the growing market for refurbished hardware.Choose second-hand and refurbished electronics.
-- Engage in sharing initiatives (device lending libraries, maker spaces) to avoid redundant consumption.
- - Participate in community repair spaces like Repair Cafés and hacklabs invested in this approach.
-When creating and maintaining software, digital tools or infrastructure:
-- Design for adaptability and resilience. Build systems that can evolve without needing constant hardware replacement.
-- Design for disassembly and repair. Favor modularity that allows parts to be easily swapped or upgraded.
-- Use salvaged components whenever possible to create new devices or applications.
-- Promote refurbished electronics both personally and professionally.
-- Leverage administrative opportunities—for example, extend device lifespans through extending legal write-off time-spans.
-- Advocate for planned longevity. Push the tech industry to create products designed to last—and to be easy to repair. Support the Right to Repair movement advocating for regulation to make planned longevity mandatory.
+---
-Principle in action & examples
-- Unbinare: https://unbina.re/ e-waste reverse engineering, hacking tools developed in collab with e-waste workers.
-- What Remains https://iodinedynamics.com/whatremains.html reusing old - NES cartridges to release new game for old NES
-- Single board computers made of repurposed fairphones https://citronics.eu/#product
-- Community initiatives, like repair cafes: https://www.repaircafe.org/en/ and Fablabs: https://fablabs.io/, various regional Right to repair initiatives.
+Care for All Hardware — Especially the Chips
+--------------------------------------------
+
+Caring for the planet also means caring for the material foundations of digital
+technology: our hardware. Every device, chip, and component originates from
+Earth’s finite resources—and eventually end up as e-waste.
+
+The production of new hardware—especially microchips, which are at the heart of
+nearly every device we use, is highly resource-intensive and energy-consuming.
+Microchips are particularly problematic because they are difficult to recycle,
+cost an immense amount of energy and resources to manufacture and their
+production is highly polluting. Maximizing the lifespan of hardware components
+is critical for reducing environmental impact and promoting a more sustainable
+and less harmful digital culture.
+
+One of the core principles of permaculture is to "produce no waste,"
+encouraging us to value and reuse all resources at hand, turning waste into a
+resource whenever possible.
+
+Digital technology cannot be produced without waste. To mitigate this
+situation, this principle calls us to step outside the capitalist model of
+perpetual consumption and growth. Instead, it invites us to recognize the
+inherent value of the devices, components, and materials we already have—and to
+care for them intentionally. Caring for the planet also means caring for the
+material foundations of digital technology: our hardware. **Every chip and
+component is made from Earth’s finite resources, and once discarded, becomes
+part of the growing e-waste crisis.**
+By acknowledging that these devices are not self-sustaining, we underscore the importance of extending their lifespan through intentional maintenance and thoughtful use.
-## Observe First
-Before taking action, it’s important to first observe. **What are the current relations? What is valuable and beautiful? What is needed? What problem are you trying to solve? Is it a social issue? Does it even require technology?** If not, refer to Principle "Not Doing". If technology is necessary, what is its purpose, and who will benefit?
+[[do you want to know more|care for all hardware - especially the chips]]
-In permaculture, before working on a piece of land, it’s essential to observe it over time, ideally through at least one full seasonal cycle. This process helps reveal insights about what can be done with minimal intervention, using limited resources and energy. Similarly, permacomputing involves carefully observing a problem or situation to create space for evaluating what needs to be done and how.
+--
-Observing can also relate to sensing the world, where computing can play a key role in strengthening ecosystems through citizen sensing and science projects. Careful observation—gathering data on air quality, water, biodiversity, local temperatures, and more—can help citizens collect the evidence needed to advocate for a healthier environment. These projects gather data on pollution, biodiversity, weather, and more, which can then be used to push for a healthier environment for both humans and non-humans.
+Observe First
+-------------
-What can YOU do?
+Before taking action, it’s important to first observe. **What are the current
+relations? What is valuable and beautiful? What is needed? What problem are you
+trying to solve? Is it a social issue? Does it even require technology?** If
+not, refer to Principle "Not Doing". If technology is necessary, what is its
+purpose, and who will benefit?
-With or without a computer:
-- Before starting any project, meeting, software development, or action, take time to do nothing and simply observe the situation from multiple perspectives. Ideally, include all stakeholders (human and non-human) in the process.
-- Join or start a citizen science or sensing project.
-- Once data is collected and evidence is gathered, collaborate with others to take action (e.g., file a lawsuit against a polluting factory, data center, or airport).
+In permaculture, before working on a piece of land, it’s essential to observe
+it over time, ideally through at least one full seasonal cycle. This process
+helps reveal insights about what can be done with minimal intervention, using
+limited resources and energy. Similarly, permacomputing involves carefully
+observing a problem or situation to create space for evaluating what needs to
+be done and how.
-When creating and maintaining software, digital tools or infrastructure:
-- Take time to observe the problem alongside the people you're designing for.
-- Incorporate sensors and data on surrounding environment into support systems
-- Assess whether the problem you're trying to solve genuinely requires computation at all. (See Principle Not Doing).
+Observing can also relate to sensing the world, where computing can play a key
+role in strengthening ecosystems through citizen sensing and science projects.
+Careful observation—gathering data on air quality, water, biodiversity, local
+temperatures, and more—can help citizens collect the evidence needed to
+advocate for a healthier environment. These projects gather data on pollution,
+biodiversity, weather, and more, which can then be used to push for a healthier
+environment for both humans and non-humans.
-Principle in action & examples
-- varia project 'stock taking sense' https://another.varia.zone/
-- Frisse wind project https://www.frissewind.nu/
-- citizen sensing project, using air quality data to enhance position of citizens when addressing problems in their environment
-- https://hollandse-luchten.org/ The UAV toolkit, an Android application making use of your smartphone's sensors for airborne science, by Then Try This https://fo.am/publications/grassroots-remote-sensing-toolkit/ and https://fo.am/activities/uav-toolkit/
+[[do you want to know more|observe first]]
---
-## Not Doing
-To reduce the resource use and waste generated by technology, embracing 'not doing' aka 'refusal' is essential for achieving degrowth. Refusal suggests a starting point of resistance and a deliberate move towards reimagining more just futures. With computing's potential to be employed in violent and oppressive ways, refusal and collective resistance and interconnected tools that need to go beyond simply turning abstract notions of justice and fairness by creating opportunities to re-evauluate foundational assumptions of technical projects and thus allowing for active re-imagination of just futures. By refusing technological inevitablility we enable forms of resistance to emerge and alternative techno-futures to be considered.
-
-The history of computing is deeply intertwined with capitalism and militarism. From playing a role in warfare and geopolitical power struggles to driving the automation of labor, computing has significantly contributed to the increased use of resources and fossil energy. The latest example of this trend is the construction of hyperscale data centers for running generative AI. Despite the promise of increased efficiency, the [Jevons Paradox](https://permacomputing.net/Jevons_paradox/) applies: higher efficiency tends to lead to greater resource use. Efficiency is often presented as a technical solution to a political issue—making decisions about how and why we use computing on a heating planet—without questioning the extractive business model.
-
-Curbing demand through refusal has proven to be one of the most effective ways to reduce computing’s harm to people and the planet, and that's where the value of 'not doing' comes in. By observing and questioning what is truly needed, we bring attention to the broader issues:** What is necessary? Who benefits? Who is harmed? And what are the impacts on the human and more-than-human environment?**
-
-What can YOU do?
-
-With or without a computer:
-- On a small scale, the act of not doing is itself a powerful contribution to sustainability. Sometimes, the greatest benefit to the planet comes from simply choosing not to act. Enjoy the pause.
-- On a larger scale, practice refusal by joining strategic efforts to reject harmful computing applications.
-- At a smaller scale, make many small everyday refusals to boycott resource-hungry, harmful (to people and/or planet) technologies or infrastructures, such as Big Tech services, in your workplace or community.
-
-When creating and maintaining software, digital tools or infrastructure:
-- Join or organize a tech worker union or strike.
-- Collectively refuse to work on harmful technologies.
-
-Principle in action & examples
-Besides the many invisible non-acts of 'not doing', projects of refusal such as the tech worker initiative 'no tech for apartheid' https://www.notechforapartheid.com/, activism against the AI powered genocide in Gaza (https://www.palestine-studies.org/en/node/1656285), activism against the arrival of data centers in your region such as citizens blocking the arrival of a Meta datacenter in Zeewolde (NL).
-But also: The SIDN case illustrates not doing as a political and infrastructural stance: refusing to treat hyperscale cloud migration as inevitable, and instead questioning the logic of outsourcing critical public internet functions to corporate platforms like AWS. See: https://www.criticalinfralab.net/wp-content/uploads/2025/04/CIL010.pdf
+Not Doing
+---------
+
+To reduce the resource use and waste generated by technology, embracing 'not
+doing' aka 'refusal' is essential for achieving degrowth. Refusal suggests a
+starting point of resistance and a deliberate move towards reimagining more
+just futures. With computing's potential to be employed in violent and
+oppressive ways, refusal and collective resistance and interconnected tools
+that need to go beyond simply turning abstract notions of justice and fairness
+by creating opportunities to re-evauluate foundational assumptions of technical
+projects and thus allowing for active re-imagination of just futures. By
+refusing technological inevitablility we enable forms of resistance to emerge
+and alternative techno-futures to be considered.
+
+The history of computing is deeply intertwined with capitalism and militarism.
+From playing a role in warfare and geopolitical power struggles to driving the
+automation of labor, computing has significantly contributed to the increased
+use of resources and fossil energy. The latest example of this trend is the
+construction of hyperscale data centers for running generative AI. Despite the
+promise of increased efficiency, the [Jevons
+Paradox](https://permacomputing.net/Jevons_paradox/) applies: higher efficiency
+tends to lead to greater resource use. Efficiency is often presented as a
+technical solution to a political issue—making decisions about how and why we
+use computing on a heating planet—without questioning the extractive business
+model.
+
+Curbing demand through refusal has proven to be one of the most effective ways
+to reduce computing’s harm to people and the planet, and that's where the value
+of 'not doing' comes in. By observing and questioning what is truly needed, we
+bring attention to the broader issues:** What is necessary? Who benefits? Who
+is harmed? And what are the impacts on the human and more-than-human
+environment?**
+
+[[do you want to know more|not doing]]
---
-## Expose The Seams
-
-Seamlessness in software obfuscates inner-workings and is a myth: things are only seamless to those who fit an idealized standard. To complicate things, software vendors often use the term "transparency" when in fact still designing interfaces in which underlying processes remain hidden to the user. However, making a technology appear transparent or seamless to users, can become an obstacle to understanding how it works, to critical engagement, and to knowledge and skill sharing. Obfuscating inner workings could also be intentional - it makes it harder to question and challenge a technology and, by extension, systematic oppressions.
-
-Exposing some of the inner-workings of infrastructure is also essential to making it tangible and to help understand meaning, motivation and materiality: **Why has it been implemented this way? How much energy does it use? What processes are happening in the background?**
-Showing the seams is important for decision making about computational processes: are they really needed? How often and how much resources should they be allowed to consume? Who needs access? Who can repair, stop or restart it?
-
-Not everything needs exposing however. Although this principle doesn't concern personal information, it can be confused with the call for full transparency which is considerably dangerous to some and undesirable for most (forced and full transparency can be dangerous to hactivists and activists alike) .
-
+Expose The Seams
+----------------
-What can YOU do
+Seamlessness in software obfuscates inner-workings and is a myth: things are
+only seamless to those who fit an idealized standard. To complicate things,
+software vendors often use the term "transparency" when in fact still designing
+interfaces in which underlying processes remain hidden to the user. However,
+making a technology appear transparent or seamless to users, can become an
+obstacle to understanding how it works, to critical engagement, and to
+knowledge and skill sharing. Obfuscating inner workings could also be
+intentional - it makes it harder to question and challenge a technology and, by
+extension, systematic oppressions.
-With or without a computer:
-- Try to spot and critically reflect the "idealised standard". We can politicise and make visible choices that impose rigid frameworks designed to force us to fit certain standrads. exclusive choice as a problem. Ask yourself: who is discriminated by the idealised standard implemented in the design of things and how can I mitigate this issue?
-- Aim to create solidarities with those who suffer from not fitting the idealized standard and must to perform extra work to make [[crappy everyday tech]] infrastructure "work". Identify and question "seamlessness" wherever it prevails and raise awareness about this persistent myth.
+Exposing some of the inner-workings of infrastructure is also essential to
+making it tangible and to help understand meaning, motivation and materiality:
+**Why has it been implemented this way? How much energy does it use? What
+processes are happening in the background?** Showing the seams is important for
+decision making about computational processes: are they really needed? How
+often and how much resources should they be allowed to consume? Who needs
+access? Who can repair, stop or restart it?
-When creating and maintaining software, digital tools or infrastructure
-- Share your projects' source code, blueprints, and design philosophy.
-- 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.
+Not everything needs exposing however. Although this principle doesn't concern
+personal information, it can be confused with the call for full transparency
+which is considerably dangerous to some and undesirable for most (forced and
+full transparency can be dangerous to hactivists and activists alike) .
-Principle in Action
-- Rosa server from the ["A Traversal Network Of Feminist Servers"](https://systerserver.net/ATNOFS/) project. Rosa exposed seams, refused to automate everything, showed different parts of the server, and also sonified some processes.
-- Run a traceroute with someone curious about how Internet works to show the many hops and countries a data packet traverses, the Internet Exchange points in between, the materiality of digital data. Also discuss why some organisations purposefuly refuse to reveal their internal networts by configuring their routers to not respond to traceroutes.
-
-Resources/Links
-- [The writing of the Cell for Digital Discomfort](https://archive2.bakonline.org/prospections/cell-for-digital-discomfort-annotated-bibliography/)
+[[do you want to know more|expose the seams]]
---
-## Consider Carefully The Interaction Between Simplicity, Complexity and Scale
+Consider Carefully The Interaction Between Simplicity, Complexity and Scale
+---------------------------------------------------------------------------
-Some simple systems need less energy, less hardware, and less maintenance. They are easier to understand, adapt, and share. By keeping things simple, we create space for care, accessibility, and long-term sustainability. At the same time, specially in relation to programming languages and hardware design, what is perceived as simple can be energy inefficient and arcane. Similarly, from scaling up datacenters to scaling up the resilience of off-the-internet wireless networks and protocols, scale is also an ambivalent notion in telecommunication, network infrastructure and topologies.
+Some simple systems need less energy, less hardware, and less maintenance. They
+are easier to understand, adapt, and share. By keeping things simple, we create
+space for care, accessibility, and long-term sustainability. At the same time,
+specially in relation to programming languages and hardware design, what is
+perceived as simple can be energy inefficient and arcane. Similarly, from
+scaling up datacenters to scaling up the resilience of off-the-internet
+wireless networks and protocols, scale is also an ambivalent notion in
+telecommunication, network infrastructure and topologies.
**There is no magic bullet.**
We acknowledge that some problems are inherently complex and achieving simplicity can be the result of a difficult and arduous process. Sometimes simplicity is simply not possible. However, this phase of questioning is rarely properly addressed. The idea of uncritically "enjoying a good challenge", combined with over-engineering and scaling up for the sake of scaling up, prevents assessing if keeping it simple will suffice. Sometimes, a partial, semi- or non-automated, supervised, or otherwise "incomplete" solution is the most appropriate choice for everyone involved.
-What can YOU do
-
-With or without a computer:
-- Let's collectively question the "unquestionable" logic of "scaling up"! Limitless growth is not the answer. Consider small-scale approaches and scaling down - can this make things more adaptable, shareable and long-lasting?
-- Don't assume you are the problem or that you don't know enough or aren't "smart enough for this". The desire for more simple systems is a legitimate and important concern which should be raised, discussed and debated. Speak out and support and encourage those who (wish to) voice these concerns.
-
-When creating and maintaining software, digital tools or infrastructure
- * Keep it human. A system should be graspable by an individual - not just specialists. If something becomes too complex to understand, it risks failing to serve the creative spirit.
- * Low complexity is beautiful. When relevant, simplicity is not a lack but a strength. More pixels, higher resolutions, or excessive layers of abstraction don’t always equal quality.
- * Avoid pseudosimplicity. Many interfaces hide how things really work, distancing users from both knowledge and action. Being transparent also about more complex aspects invites understanding and shared agency.
- * Reduce dependencies. Relying on fewer external tools - whether hardware, software, or libraries - keeps systems flexible and independent.
- * Value wisdom over accumulation. Instead of endlessly expanding codebases, we can build knowledge and skills that outlast specific tools or technologies.
- * Think abundantly. Computing is often framed in terms of limits, but history shows that creativity thrives within constraints. What can we do with kilobytes instead of gigabytes? With slower cycles rather than infinite speed? Thinking in terms of enough rather than always more opens new possibilities.
-
-Principle in Action
-- [Small File Photo Festival](https://unthinking.photography/projects/smallfil)
-- [Small File Media Festival](https://smallfile.ca)
-- [Oberon OS](https://en.wikipedia.org/wiki/Oberon_(operating_system))
-- [On not scaling LURK](https://txt.lurk.org/on-not-scaling-lurk/)
+[[do you want to know more|consider carefully the interaction between simplicity complexity and scale]]
---
-## Keep it flexible
-
-Flexibility means adaptability to different purposes and circumstances, including ones that were never even considered by the original designer. While we value simplicity, we know that very simple systems can also be inflexible, and this principle exists as a counterweight to that kind of oversimplicity. Ideally, one should aim at a mutually supportive balance between simplicity and flexibility.
-
-Computing systems should adapt to the changes in their operating environments (especially in relation to energy and heat). 24/7 availability of all parts of the system should not be required, and neither should a constant operating performance (e.g. networking speed).
+Keep it flexible
+----------------
-If it is possible to imagine all the possible use cases when designing a system, the design may very well be too simple and/or too inflexible. Smallness, simplicity and flexibility are also part of the "small, sharp tools" ideal of the [[Unix]] command line. Here the key to flexibility is the ability to creatively combine small tools that do small, individual things.
+Flexibility means adaptability to different purposes and circumstances,
+including ones that were never even considered by the original designer. While
+we value simplicity, we know that very simple systems can also be inflexible,
+and this principle exists as a counterweight to that kind of oversimplicity.
+Ideally, one should aim at a mutually supportive balance between simplicity and
+flexibility.
+Computing systems should adapt to the changes in their operating environments
+(especially in relation to energy and heat). 24/7 availability of all parts of
+the system should not be required, and neither should a constant operating
+performance (e.g. networking speed).
-What can YOU do
+If it is possible to imagine all the possible use cases when designing a
+system, the design may very well be too simple and/or too inflexible.
+Smallness, simplicity and flexibility are also part of the "small, sharp tools"
+ideal of the [[Unix]] command line. Here the key to flexibility is the ability
+to creatively combine small tools that do small, individual things.
-With or without a computer:
-- Identifying inflexibilities in digital systems can be simple (e.g. it breaks immediately) or difficult (e.g. it refuses to work in some way but it's very unclear why). It is important to not give up in both cases. Is it reasonable that the system is inflexible in this way? Can we raise this as a discussion with the designers?
-- You do not have to be always available yourself. Speaking of flexibility, if we collectively refuse to always being available, our devices don't have to always be on, online, at full speed either.
-
-When creating and maintaining software, digital tools or infrastructure
-- Consider the idea of static and runtime flexibility. Static flexibility defines what the system can do in general, whereas runtime flexibility refers to how it can adapt to a changing environment (e.g. changes in temperature, energy and network availability).
-- Computing technology in general is very flexible because of its programmability. Programming and programmability should be supported and encouraged everywhere, and artificial lock-ins that prevent (re)programming should be broken.
-- Design systems you can gradually modify and improve while running them. In this some case this could also means designing a self-obviating system meaning systems systems designed to become redundant through their own successful operation.
-- In a long term, software and hardware systems should not get obsoleted by changing needs and conditions. New software can be written even for old computers, old software can be modifed to respond to new needs, and new devices can be built from old components.
-
-Principle in Action
-- [solar.lowtechmagazine.com](https://solar.lowtechmagazine.com/about/the-solar-website/)
-- [remote.materialsmatter.ie](https://remote.materialsmatter.ie)
+[[do you want to know more|keep it flexible]]
---
-## Build on solid ground
-
-Consider when to build on solid ground and when to design for disappearance. If longetivity is required some considerations are needed.
-
-Many computing systems are based on platforms, frameworks or even languages that change very rapidly, may become obsolete at any time, and are too complex to be easily reimplemented. This principle exists to minimize [obsolescence](https://permacomputing.net/obsolescence/) and superfluous maintenance work in systems intended to last.
-
-It is good to experiment with new ideas, concepts and languages, but forming hard dependencies on them is usually a bad idea. Appreciate mature technologies, clear ideas and well-understood theories when building something that is intended to last. Software that uses open, well-documented standards will be more useful in communicating with the wider technological world. It also means that data can survive and still be readable even if the software is no longer functioning.
+Build on solid ground
+---------------------
+Consider when to build on solid ground and when to design for disappearance. If
+longetivity is required some considerations are needed.
-What can YOU do
+Many computing systems are based on platforms, frameworks or even languages
+that change very rapidly, may become obsolete at any time, and are too complex
+to be easily reimplemented. This principle exists to minimize
+[obsolescence](https://permacomputing.net/obsolescence/) and superfluous
+maintenance work in systems intended to last.
-With or without a computer:
- - Consider using software that runs locally, is open-sourced, and has a thriving user community or is well-documented
- * Try to pick software that favours slow release cycles and thorough testing over rolling updates.
- * try to use smaller, more general-purpose tools instead of complex, prescriptive all-in-one solutions
- * You may also read this as "grow roots to a solid ground". Learn things that last. Learn the history of the technology you use.
+It is good to experiment with new ideas, concepts and languages, but forming
+hard dependencies on them is usually a bad idea. Appreciate mature
+technologies, clear ideas and well-understood theories when building something
+that is intended to last. Software that uses open, well-documented standards
+will be more useful in communicating with the wider technological world. It
+also means that data can survive and still be readable even if the software is
+no longer functioning.
-When creating and maintaining software, digital tools or infrastructure
- * Avoid unreliable dependencies, especially those hard (non-optional) dependencies. If you can't work around them (in case of software), you should bundle them directly with your software. Keep local copies, instead of relying on downloading them from external servers every time. This way, your software won’t break if those external resources disappear.
- * It is possible to support several target platforms. In case of lasting programs, one of these should be a bedrock platform, or instruction set, that does not change too much and therefore increase accessibility, portability and fallback scenarios.
- * Imagine some of your users will never be able to get an update or find support - think about how they might solve their problems.
- * Try to use standard file and data exchange formats, ideally formats that are human-readable.
- * Don't take anything for granted. Especially don't expect the infrastructure such as the power grid and global networking to continue working indefinitely.
-
-Principle in action:
- * UXN - https://wiki.xxiivv.com/site/uxn.html
- * DuskOS - https://duskos.org/
- * Actually Portable Executable - https://justine.lol/ape.html
- * Static HTML Site Generators - https://permacomputing.net/static_site_generator
+[[do you want to know more|build on solid ground]]
---
-## (Almost) Everything has a place
-
-There is a place for almost everything. Nothing is obsolete or irrelevant. Even if they lose their original meaning and context, most programmable systems may be readapted to new purposes they were not originally designed for. Think about technology as a rhizome rather than a "highway of progress and constant obsolescence".
-
-Computing is often framed as a kind of ideal universal medium. But the reality is that **computing is culture!** It can be very diverse, full of the color, contingency and expression that is part of any cultural production. Sadly in practice, and in its current form with military industrial roots, this culture exists mostly to reproduce and reinforce existing power structures within societies and support ecomic growth. Today's computing cultures are still dominated by Human Interface Guidelines designed and controlled by a small groups of people with similar backgrounds, priorities and values. But if we can let go of some of the ideas of technological conformity, we might start to see a much wider spectrum of possible ways of computing, some of which might better reflect local needs, desires and societal issues.
-
-This can also open to much wilder and diverse creative practices and aesthetics.
-
+(Almost) Everything has a place
+-------------------------------
-What can YOU do
+There is a place for almost everything. Nothing is obsolete or irrelevant. Even
+if they lose their original meaning and context, most programmable systems may
+be readapted to new purposes they were not originally designed for. Think about
+technology as a rhizome rather than a "highway of progress and constant
+obsolescence".
-With or without a computer:
-* situate your work
-* avoid falling too quickly in extremely universal or extremely singular perspectives. Adopt a more archipelagic vision that departs from local vs global binary oppositions.
-* While operating locally and at present, be aware of the entire world-wide context your work takes place in. This includes the historical context several decades to the past and the future. Understanding the past(s) is the key for envisioning the possible futures.
+Computing is often framed as a kind of ideal universal medium. But the reality
+is that **computing is culture!** It can be very diverse, full of the color,
+contingency and expression that is part of any cultural production. Sadly in
+practice, and in its current form with military industrial roots, this culture
+exists mostly to reproduce and reinforce existing power structures within
+societies and support ecomic growth. Today's computing cultures are still
+dominated by Human Interface Guidelines designed and controlled by a small
+groups of people with similar backgrounds, priorities and values. But if we can
+let go of some of the ideas of technological conformity, we might start to see
+a much wider spectrum of possible ways of computing, some of which might better
+reflect local needs, desires and societal issues.
-When creating and maintaining software, digital tools or infrastructure
- * Every system, no matter how ubiquitous or "universal" it is, is only a tiny speckle in a huge ocean of possibilities. Try to understand the entire possibility space in addition to the individual speckles you have concrete experience about.
- * Appreciate diversity, avoid monoculture. But remember that standards can also have an important place.
- * Strict utilitarianism impoverishes. Uselessness also has an important place, so appreciate it.
- * There is a place for both slow and fast, both gradual and one-shot processes. Don't look at all things through the same glasses.
+This can also open to much wilder and diverse creative practices and
+aesthetics.
-Principles In Action:
- * TeamSpeak - old versions of a gaming chat platform used by Cubans who have little access to the wider internet: https://qbared.com/ts/
- * Rustic Computing - https://wintermute.org/project/Rustic_Computing/
- * Gemini Protocol - https://geminiprotocol.net/
+[[do you want to know more|(almost) everything has a place]]
---
-## Integrate biological and renewable resources
-
-Permacomputing seeks to support sustainable and regenerative practices, playing a beneficial role in natural ecosystems, but until we can grow computers on trees, this goal remains largely aspirational. The whole electronic industry is based on using some of the most artificial materials ever created. The majority of computer components are firmly tied to complex, extractive and exploitative manufacturing processes linked to the semi-conductory industry. There is an increasing incentive and an increasing number of experiments to replace some physical parts of digital hardware with more sustainable materials, while rethinking how supply chains can be more ethical. How can this be encouraged? How can this be priositised? How can this be more than symbolic or marketting?
-
-In the same sense, we can think of energy use, not just in terms of efficiency but also in terms of local impact. Stemming from the observed principle, see to what extent it is possible to work with (local) biological and renewable materials and resources. Not only does this minimise the ecological footprint of the supply chain, it also allows for a closer relation to nature. By using more basic kinds of materials, we attend to the labour of making which pushes us to reflect on conditions, resources, and access to resources as well as how energy is generated, materials decompose and matter is recycled. Crafting, DIY and idiosyncratic approaches to hardware design can help situate computing culture and reveal points of frictions.
-
-Some General Considerations:
- * Prefer systems that use lower power and limited network traffic
- * Mod, repair and customize your devices with natural materials and embrace a wide range of aesthetics (post-digital, intermedia, traditional, etc).
- * Use bioenergy and decomposition
-
-If you are designing or building systems:
- * Create low-power systems that strengthen the biosphere and use the wide-area network sparingly.
- * Minimize the use of fossil fuels and mineral resources.
- * Don't create systems that obfuscate waste.
- * Try to use natural, local materials whenever you can: wood, ceramics, stone, textiles
- * Design and build for older, reused materials and equipment
-
-Principle in action
- * Clay PCB: https://feministhackerspaces.cargo.site/Clay-PCB
- * Solar Protocol: https://solarprotocol.net/
- * The first mouse was made of wood, a modern one could be too: https://en.wikipedia.org/wiki/Computer_mouse#/media/File:Firstmouseunderside.jpg
- * LivingLab: https://lab.node9.org/
- * Southern principles https://permacomputing.net/sister0/
+Integrate biological and renewable resources
+--------------------------------------------
+
+Permacomputing seeks to support sustainable and regenerative practices, playing
+a beneficial role in natural ecosystems, but until we can grow computers on
+trees, this goal remains largely aspirational. The whole electronic industry is
+based on using some of the most artificial materials ever created. The majority
+of computer components are firmly tied to complex, extractive and exploitative
+manufacturing processes linked to the semi-conductory industry. There is an
+increasing incentive and an increasing number of experiments to replace some
+physical parts of digital hardware with more sustainable materials, while
+rethinking how supply chains can be more ethical. How can this be encouraged?
+How can this be priositised? How can this be more than symbolic or marketting?
+
+In the same sense, we can think of energy use, not just in terms of efficiency
+but also in terms of local impact. Stemming from the observed principle, see to
+what extent it is possible to work with (local) biological and renewable
+materials and resources. Not only does this minimise the ecological footprint
+of the supply chain, it also allows for a closer relation to nature. By using
+more basic kinds of materials, we attend to the labour of making which pushes
+us to reflect on conditions, resources, and access to resources as well as how
+energy is generated, materials decompose and matter is recycled. Crafting, DIY
+and idiosyncratic approaches to hardware design can help situate computing
+culture and reveal points of frictions.
+
+[[do you want to know more|integrate biological and renewable resources]]
