structuring this random pile of documents

preparatory to making it actually accessible

docs/mkdocs.sh

@@ -91,6 +91,31 @@ do
  fi
 done
 cd ..
+cd setup
+options=$osoptions"--toc -N --toc-depth=5 --wrap=preserve --metadata=lang:en --include-in-header=./icon.pandoc  --include-before-body=$templates/before.pandoc --css=$templates/style.css --include-after-body=$templates/after.pandoc -o"
+pwd
+for f in *.md
+do
+ len=${#f}
+ base=${f:0:($len-3)}
+ if [ $f -nt $base.html ];
+ then
+   katex=""
+   for i in 1 2 3 4
+   do
+     read line
+     if [[ $line =~ katex ]];
+     then
+         katex=" --katex=./"
+     fi
+   done <$f
+   echo "generating $base.html from $f"
+   pandoc $katex $options $base.html $base.md
+ #else
+ #  echo "       $base.html up to date"
+ fi
+done
+cd ..
 cd rootDocs
 pwd
 katex=""

docs/rootDocs/NOTICE.md

@@ -19,4 +19,4 @@ This product includes several packages, each with their own free software licenc
 
 Or, in the case of Sqlite, the Sqlite blessing in place of a license, which is
 morally though not legally obligatory on those that obey the
-commandments of Gnon.  See also the [contributor code of conduct](docs/contributor_code_of_conduct.html).
+commandments of Gnon.  See also the [contributor code of conduct](docs/setup/contributor_code_of_conduct.html).

docs/rootDocs/README.md

@@ -74,7 +74,7 @@ git config --local include.path ../.gitconfig
 this will substantially mitigate the problem of submodules failing to
 update in pushes, pulls, checkouts, and switches.
 
-[cryptographic software is under attack]:./docs/contributor_code_of_conduct.html#code-will-be-cryptographically-signed
+[cryptographic software is under attack]:./docs/setup/contributor_code_of_conduct.html#code-will-be-cryptographically-signed
 "Contributor Code of Conduct"
 {target="_blank"}
 

docs/setup/icon.pandoc

@@ -0,0 +1 @@
+	<link rel="shortcut icon" href="../rho.ico">

docs/social_networking.md

@@ -353,9 +353,17 @@ unlimited power, nor allow them to be a central point of failure.
 
 ### runningt in schism, with many approximately equal branches
 
+Centralized databases are a single point of failure.  They are also extremely
+convenient, because they enable many humans to leverage the judgment of
+a single human, rather than needing to exercise their own judgement.
+
+With Git, you usually have one master repository.  Sometimes you do not,
+and have to exercise your own judgement.  I have often enough tripped
+over this, and often enough managed fine.
+
 Under attack, the system may well schism, with no one source that lists all
 or most Zooko identities that people are interested in contacting, but it
-should, like git, be designed to schism, and work well enough while
+should, like Git, be designed to schism, and work well enough while
 schismed.  That is what makes Git centralization truly decentralized.
 Sometimes, often, there is no one authoritative branch, and things still work.