permacomputing

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

commit 7ed038b89d1f095e8c20d3bf029cfe0ce0a371f2
parent 51a36b9662e506260df8a595ffed801a7f95a985
Author: ugrnm <ultrageranium@bleu255.com>
Date:   Fri,  6 Jun 2025 10:51:28 +0200

hope for tweaks

Diffstat:
Mhope_for_the_best_prepare_for_the_worst.mdwn | 21+++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/hope_for_the_best_prepare_for_the_worst.mdwn b/hope_for_the_best_prepare_for_the_worst.mdwn @@ -1,8 +1,25 @@ -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. 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. +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. 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? +---------------- -With or without a computer: - Learn how to make, fix, and repurpose things yourself—and share equipment and skills within your community (e.g., participate in repair cafés). - Build local relationships: get to know your neighbors and their (technical) skills. Collaborate, exchange, and build for mutual resilience. - Favor local storage (personal file collections, offline archives) rather than depending solely on online content services. +With or without a computer: + +* Learn how to make, fix, and repurpose things yourself—and share equipment and +skills within your community (e.g., participate in repair cafés). +* Build local relationships: get to know your neighbors and their (technical) +skills. Collaborate, exchange, and build for mutual resilience. +* Favor local storage (personal file collections, offline archives) rather than +depending solely on online content services. When creating and maintaining software, digital tools or infrastructure: - Build systems that are resilient to intermittent energy supply and network connectivity. - Distributed computing approaches could offer greater resilience. However, their overall environmental footprint needs careful evaluation—distributed systems may be robust but not always energy-efficient. - Take inspiration from operating systems that can be installed on old or salvaged hardware, enabling continued computation even under conditions of technological scarcity. (lightweight Linux distributions, Collapse OS, Rockbox, etc).