commit aa82e5351d2583cbd9a419fa0a3745239addb82e parent a1dc9265139e44814f8fa75aeeed6cb0feb9050a Author: Nick Moffitt <nick@zork.net> Date: Wed, 20 May 2026 15:38:36 +0100 fix early bits Diffstat:
| M | spacehobo/antipatterns.mdwn | | | 4 | +--- |
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/spacehobo/antipatterns.mdwn b/spacehobo/antipatterns.mdwn @@ -13,9 +13,7 @@ In the abstract, I hope to illustrate the ways in which Permacomputing is not an # Permacomputing is not Hierarchical -One of the reasons that people have trouble understanding definitions is that we deliberately avoid them. We have certain shared concerns and goals, but don't define "permacomputing kits" or formal lists of "permacomputing tools". - -## Permacomputing is not Prescriptive +One of the reasons that people have trouble understanding definitions is that we deliberately avoid them. We have certain shared concerns and goals, but don't define "permacomputing kits" or formal lists of "permacomputing tools". There is no Permacomputing Certification Authority to rule on how "perma" your computer is. One resource that shows up prominently in search results is the [Hundred Rabbits talks on Permacomputing](https://100r.co/site/permacomputing_101.html) by Devine Lu Linvega. Their practice involves low-power disconnected living on a sailboat in the Pacific Ocean, and they have developed tools such as [[Uxn]] in service of this. A lot of the writing about Permacomputing comes from their lived experience and that of their shared communities of practice online.