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 2d1ac07bd1c79e88642487b0ee72d73521184e5f
parent 80c90646c6f01bbddc9acdbb94699cfbf85f6ea7
Author: Ville-Matias Heikkila <viznut@low.fi>
Date:   Wed,  8 Jun 2022 13:19:49 +0300

Merge branch 'master' of bleu255.com:/var/www/git.bleu255.com/repos/permacomputing

Diffstat:
MPrinciples.mdwn | 2+-
MTODO.mdwn | 5+++--
Mlocal.css | 10++++++++++
Mtemplates/page.tmpl | 2+-
4 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/Principles.mdwn b/Principles.mdwn @@ -53,7 +53,6 @@ philosophical ones, so feel free to disagree with them or refactor them. * Computers were invented to assist people in their cognitive processes. "Intelligence amplification" was a good goal, but intelligence may also be used narrowly and blindly. It may therefore be a better idea to amplify awareness. * Awareness means awareness of whatever is concretely going on in the world/environment but also awareness of how things work and how they situate in their contexts (cultural, historical, biological etc). * You don't need to twiddle with everything in order to understand it. [[Yin hacking]] emphasizes observation. -* Make the computer visualize/auralize its internal state as well as whatever it knows about the state of its physical environment. Regard this visualization/auralization as a background landscape: facilitate observation but don't steal the attention. Also, don't use too much computing resources for the visualization/auralization. * It may also often be a good idea to amplify the computer's awareness of its physical surroundings with things like sensors. ## Expose everything @@ -61,6 +60,7 @@ philosophical ones, so feel free to disagree with them or refactor them. * As an extension of "amplify awareness": Don't hide information! * Keep everything open, modifiable and flexible. * Share your [[source code|FLOSS]] and design philosophies. +* Make the computer visualize/auralize its internal state as well as whatever it knows about the state of its physical environment. Regard this visualization/auralization as a background landscape: facilitate observation but don't steal the attention. Also, don't use too much computing resources for the visualization/auralization. ## Respond to changes diff --git a/TODO.mdwn b/TODO.mdwn @@ -3,7 +3,7 @@ To keep track of things [[TODO]] before launching the wiki: * cloning/local reading instructions * footnotes how * <s>better bottom links: About, LICENSE, Contact</s> -* no italic for bottom links +* <s>no italic for bottom links</s> * weird scrollbar on code * section on community * <s>layout CC0</s> @@ -15,5 +15,6 @@ To keep track of things [[TODO]] before launching the wiki: * section for curriculum postdoc thing * look into the file upload plugin for images and stuff * decide on policy for images (ditherpunk?) -* stagit URLs for page changes/history? +* <s>stagit URLs for page changes/history?</s> NOPE stagit does not generate static pages indiv file history, too expensive * <s>make a default comment for empty web commits to improve stagit browsing</s> +* LOGO! diff --git a/local.css b/local.css @@ -5,3 +5,13 @@ code { a { text-decoration: none; } + +.bottom_menu { + display: block; + margin-top: 1em; +} + +.last_edit { + font-style: italic; +} + diff --git a/templates/page.tmpl b/templates/page.tmpl @@ -192,7 +192,7 @@ Links: </TMPL_IF> <div class="bottom_menu"> -<a href="/about/">About</a> | <a href="/contact/">Contact</a> |<a href="/license/">LICENSE</a> | <span class="pagedate">Last edit <TMPL_VAR MTIME></span> +<a href="/about/">About</a> | <a href="/contact/">Contact</a> | <a href="/license/">LICENSE</a> | <span class="last_edit">Last edit <TMPL_VAR MTIME></span> <!-- Created <TMPL_VAR CTIME> --> </div>