commit 05aa3d7a03b5cf2f912312514ebd2fd1bb860bda
parent 136ac6a39d0adb5aea1bcac3b59f119f00dd25cd
Author: ugrnm <ultrageranium@bleu255.com>
Date: Fri, 6 Nov 2026 12:44:31 +0100
Merge branch 'master' of eik:/var/www/git.permacomputing.net/repos/permacomputing
Diffstat:
11 files changed, 87 insertions(+), 79 deletions(-)
diff --git a/Community.mdwn b/Community.mdwn
@@ -15,7 +15,7 @@ adjacent practices we feel strongly connected to:
* **DE**, Berlin: **[Berlin permacomputing community](https://berlin.permacomputing.net)** at [Offline](https://offline.place/)
* **ES**, Barcelona: **[Permacomputing Barcelona](https://barcelona.permacomputing.net)**
* **NL**, Rotterdam: **[Permacomputing Rotterdam](https://rotterdam.permacomputing.net)** at [Varia](https://varia.zone)
-* **Tas**: **[Autolumi](https://www.autoluminescence.institute/)** lutruwtia/Tas, Aus
+* **Tas**: **[Autolumi](https://autolumi.net/)** lutruwtia/Tas, Aus
* **UK**, London: **[Permacomputing Club](https://london.permacomputing.net)** at SET Social
* **US**, New York City: **[NYC permacomputing meetup](https://nyc.permacomputing.net)**
* **US**, Philadelphia: **[Iffy Books](https://iffybooks.net/about/)**
@@ -55,3 +55,8 @@ Finding permacomputing content on the Fediverse:
* **[#permacomputing](https://mastodon.social/tags/permacomputing)**: obvious hashtag is obvious
+Forum
+--------
+
+* **A non-federated forum based on [cerca](https://cblgh.org/cerca/):** [bbs.permacomputing.net](http://bbs.permacomputing.net)
+
diff --git a/about.mdwn b/about.mdwn
@@ -7,7 +7,7 @@ Is this for you?
Are you looking to understand the effects of computer use in your community, experiment with projects, create art about alternative futures, and/or join or organize local groups? Then yes! And there's more about these ideas in [[getting_started]].
-At the same time, we're not here to help you [[greenwash|greenwashing]] your new "sustainable" technology startup, green AI, ecological web3 funding, circular crypto carbon credit program, and other nonsensical technosolutionist forms of climate denial and white [re]centering privilege. For these cases, please go elsewhere :)
+At the same time, we're not here to help you [[greenwash|greenwashing]] your new "sustainable" technology startup, green AI, ecological web3 funding, circular crypto carbon credit program, and other nonsensical technosolutionist forms of climate change denial and white [re]centering privilege. For these cases, please go elsewhere :)
Contact us!
diff --git a/eik.mdwn b/eik.mdwn
@@ -102,7 +102,7 @@ This relies on an environment variable in `/root/.acme.sh/acme.sh.env` called `G
cerca
-----
-We maintain a single patch on `bbs-patches` to disable registration (See below for how we manage this with our own Git hosting).
+We maintain a customised version of [Cerca](https://cblgh.org/cerca/). We work to upstream all our changes in conversation with `@cblgh`, the maintainer. Some of our changes are still under consideration and might not be applicable for the wider Cerca community. The conversation is ongoing over on [the issue tracker](https://github.com/cblgh/cerca/issues).
Our system configuration documentation has been upstreamed to [`docs/hosting.md`](https://github.com/cblgh/cerca/blob/main/docs/hosting.md) 🎉
diff --git a/index.mdwn b/index.mdwn
@@ -25,17 +25,19 @@ understand the purpose and ethos of this project :)
For more information:
* [[A longer introduction|Permacomputing]]
-* [[Principles|principles]] for using and designing computational systems
-* [[Issues]] in today's computing
+* [[Characteristics of computational systems|Properties]]
+* [[Permacomputing design principles|principles]]
-Resources:
+Network:
+* [[Community]] - meet, work, organise and discuss with us!
* [[Getting Started]] - a starter's manual of some sort
+
+Resources:
+
* [[Library]] - texts and media about and around permacomputing
* [[Projects]] - selection of projects affiliated with or adjacent to permacomputing
* [[Assessments]] - review and analysis of existing and established pieces of technology
* [[Workshop]] - collection of reproducible experiments
-Network:
-* [[Community]] - meet, work, organise and discuss with us!
diff --git a/issues.mdwn b/issues.mdwn
@@ -1,32 +0,0 @@
-There are several issues in today's computing.
-
-If the information and communications technology (ICT) industry was purposefully
-following a harmful agenda, these would probably be their design principles:
-
-* disregard for life
-* disregard for the chips
-* more is better
-* assume limitless resources
-* keep it controlled
-* outsource the problem
-* amplify ignorance
-* obfuscate everything
-* destroy communities
-* achieve monopoly
-
-While the industry is rarely discussed in this way, there are increasingly
-well-documented issues in the dominant computational cultural paradigm which all
-together help better explain how such a harmful agenda can emerge explicitly or
-implicitly.
-
-Additional topics to explore:
-
-* **inaccessible:** [[greenwashing]], [[Californian ideology]], [[otherness]],
- [[pseudosimplicity]]
-* **incompatible:** vendor lock-in, proprietary
-* **inefficient:** [[bloat]], [[maximalism]], [[cryptocurrency]],
- [[calculation factory]], [[cornucopianism]]
-* **rigid:** [[monoculture]], [[siliconization]]
-* **failing:** [[silver bullet]], [[planned obsolescence]], [[wishcycling]],
- [[software rot]]
-* **extractivist:** attention economy, capitalism, [[Big Tech]], neoliberalism
diff --git a/onboarding.mdwn b/onboarding.mdwn
@@ -83,14 +83,14 @@ Eik. For example,
- [x] Migrate wiki from borok to eik
- [x] Connect wiki to Rauthy
- [x] Add Rauthy support to Cerca (web forum)
-- [ ] Document new sysadmin reality (Rauthy, SFTP, etc.)
-- [ ] Editorial guideline for wiki
+- [x] Document new sysadmin reality (Rauthy, SFTP, etc.)
+- [] Editorial guideline for wiki
#### Migration hell
-- [ ] Cerca user migrations (LURK SMTP, group mail testing, etc.)
-- [ ] Migrate web ssh users to new SFTP setup
-- [ ] Cleanup dormant user accounts on eik
+- [x] Cerca user migrations (LURK SMTP, group mail testing, etc.)
+- [x] Migrate web ssh users to new SFTP setup
+- [x] Cleanup dormant user accounts on eik
#### On the way out
diff --git a/permacomputing.mdwn b/permacomputing.mdwn
@@ -32,34 +32,3 @@ aesthetics, virtual does not mean immaterial and doing things with less is not
_a return to the past_. We want to investigate what a permacomputing way of
life could be, and what sort of transformative computational culture and
aesthetics it could bring forward.
-
-The [[principles]] of permacomputing are:
-
- * Hope for the Best, Prepare for the Worst
- * Care for All Hardware — Especially the Chips
- * Observe First
- * Not Doing
- * Expose the Seams
- * Consider Carefully the Interaction Between Simplicity, Complexity and Scale
- * Keep It Flexible
- * Build on Solid Ground
- * (Almost) Everything has a place
- * Integrate Biological and Renewable Resources
-
-Properties of permacomputing systems
-------------------------------------
-
-The principles concretely manifest themselves in various forms so as to
-highlight the following properties:
-
-* **accessible**: well documented and adaptable to an individual's needs.
-* **compatible**: works on a variety of architectures.
-* **efficient**: uses as little resources (power, memory, etc) as possible ([[minimization]]).
-* **flexible**: modular, portable, adapts to various use-cases.
-* **resilient**: repairable, [[offline-first|offline first]], low-maintenance, designed for disassembly, [[planned for longevity|planned longevity]], [[maximized lifespan|lifespan maximization]], descent-friendly or [[designed for descent|design for descent]]
-
-Some additional concerns are of indirect interest because they impose costs on the entire end-to-end process of software creation:
-
-* it's [[bootstrapped|bootstrapping]] from machine code without circular reasoning (bootstrappable builds)
-* it's obvious what source code went into it (reproducible builds)
-* it's easy to audit its source code, including all dependencies
diff --git a/programming_languages.mdwn b/programming_languages.mdwn
@@ -26,4 +26,4 @@ There is a high diversity of possible tasks and programs, and different programm
See also:
* [Drew DeVault's blog post about benchmarking compilers by Hello world size](https://drewdevault.com/2020/01/04/Slow.html)
- * [Blog post about a research in energy efficiency of programming languages](https://www.sendung.de/2022-07-24/programming-languages-energy-efficiency/)
+ * [Blog post about energy efficiency of programming languages](https://www.sendung.de/2022-07-24/programming-languages-energy-efficiency/) and final [research article](https://dl.acm.org/doi/10.1145/3136014.3136031)
diff --git a/properties.mdwn b/properties.mdwn
@@ -0,0 +1,63 @@
+Computational systems today
+---------------------------
+
+If the information and communications technology (ICT) industry was purposefully
+following a harmful agenda, these would probably be their design principles:
+
+* disregard for life
+* disregard for the chips
+* more is better
+* assume limitless resources
+* keep it controlled
+* outsource the problem
+* amplify ignorance
+* obfuscate everything
+* destroy communities
+* achieve monopoly
+
+While the industry is rarely discussed in this way, there are countless
+well-documented proofs that the dominant computational cultural paradigm greatly accelerates harm.
+
+The characteristics of such systems are:
+
+* **inaccessible:** [[greenwashing]], [[Californian ideology]], [[otherness]],
+ [[pseudosimplicity]]
+* **incompatible:** vendor lock-in, proprietary
+* **inefficient:** [[bloat]], [[maximalism]], [[cryptocurrency]],
+ [[calculation factory]], [[cornucopianism]]
+* **rigid:** [[monoculture]], [[siliconization]]
+* **failing:** [[silver bullet]], [[planned obsolescence]], [[wishcycling]],
+ [[software rot]]
+* **extractivist:** attention economy, capitalism, [[Big Tech]], neoliberalism
+
+
+Permacomputing systems
+----------------------
+
+The design [[principles]] of permacomputing systems are:
+
+ * Hope for the Best, Prepare for the Worst
+ * Care for All Hardware — Especially the Chips
+ * Observe First
+ * Not Doing
+ * Expose the Seams
+ * Consider Carefully the Interaction Between Simplicity, Complexity and Scale
+ * Keep It Flexible
+ * Build on Solid Ground
+ * (Almost) Everything has a place
+ * Integrate Biological and Renewable Resources
+
+The characteristics of such systems are:
+
+* **accessible**: well documented and adaptable to an individual's needs.
+* **compatible**: works on a variety of architectures.
+* **efficient**: uses as little resources (power, memory, etc) as possible ([[minimization]]).
+* **flexible**: modular, portable, adapts to various use-cases.
+* **resilient**: repairable, [[offline-first|offline first]], low-maintenance, designed for disassembly, [[planned for longevity|planned longevity]], [[maximized lifespan|lifespan maximization]], descent-friendly or [[designed for descent|design for descent]]
+
+Some additional concerns are of indirect interest because they impose costs on the entire end-to-end process of software creation:
+
+* it's [[bootstrapped|bootstrapping]] from machine code without circular reasoning (bootstrappable builds)
+* it's obvious what source code went into it (reproducible builds)
+* it's easy to audit its source code, including all dependencies
+
diff --git a/unbrick01.mdwn b/unbrick01.mdwn
@@ -2,7 +2,7 @@
## Unlocking the bootloader
-- set up the Android phone.
+- set up the Android phone. >>x
- connect to Wi-Fi (mandatory for `OEM unlocking option to show up`)
- navigate to the phone’s settings
- all the way at the bottom press on `About Phone`
@@ -10,7 +10,7 @@
- press `back` twice and scroll down to `Developer Options`
- enable `OEM unlocking` and `USB debugging`. If `OEM unlocking` is not there, reboot the phone and try again.
-## Installation Heimdall
+## Installation Heimdall >>x
Two options: use the version provided by your OS, or compile from scratch if your OS does not provide a `heimdall` binary, or if this binary is too old. We need at least `v2.2.2`.
diff --git a/unbrick01/discussion.mdwn b/unbrick01/discussion.mdwn
@@ -0,0 +1 @@
+test
