Linkbar is now working, if only in the manifesto subdirectory.

Finally going public with it.  Linked it from my reaction.la
web index, so should become visible to search engines bye and bye

docs/manifesto/Revelation.md

@@ -45,11 +45,17 @@ Deliveries would only be delivered to a name and address registered to a social
 
 If you can use cash, gold, silver, tobacco, anonymous crypto currency, or small calibre long rifle ammunition to buy and sell, then the prophecy of the beast has not yet come to pass.
 
+[soft]: May_scale_of_monetary_hardness.html
+{target="_blank"}
+
 Crypto currency has the great advantage that you can use it to perform
 transactions over distance and time, secured by the blockchain, and
-rhocoin is designed to also allow instant in person on-the-spot
+rhocoin will enable allow instant in person on-the-spot
-over-the-counter transactions, intended to be a complete replacement
+over-the-counter transactions, designed intended to be a complete replacement
-for fiat money.
+for fiat money.  (Though over the counter instant transactions require money that
+remains [soft] for several minutes, but this is a big improvement over credit cards,
+which remain [soft] for a few months, cheques that remain soft for days,
+and wire transfers that remain [soft] for hours.)
 
 It is increasingly the case that low, poor, and bond, face considerable risks
  in using cash. For example black people, mainly black people who do not have
@@ -102,7 +108,7 @@ Tensions over the dangerously powerful global financial system are a large part
 of the current proxy war between the Global American Empire and Russia,
 and the looming wars with China and Iran.  If the prophecy comes to pass,
 the nukes are going to fly.  Which will probably not be the end times either,
-but will have a more than passing resemblance.
+but will have more than a passing resemblance.
 
 As a blockchain scales up to full commercial scale, running a full peer
 becomes costly and burdensome, so with bitcoin we have alarmingly few

docs/manifesto/mkdocs.sh

@@ -0,0 +1,39 @@
+#!/bin/bash
+set -e
+cd `dirname $0`
+docroot="../"
+banner_height=banner_height:15ex
+templates=$docroot"pandoc_templates"
+if [[ "$OSTYPE" == "linux-gnu"* ]]; then
+		osoptions=""
+elif [[ "$OSTYPE" == "darwin"* ]]; then
+		osoptions=""
+elif [[ "$OSTYPE" == "cygwin" ]]; then
+		osoptions="--fail-if-warnings  --eol=lf "
+elif [[ "$OSTYPE" == "msys" ]]; then
+		osoptions="--fail-if-warnings  --eol=lf "
+fi
+options=$osoptions"--toc --number-sections --toc-depth=5 --from markdown+smart+raw_html+fenced_divs+bracketed_spans --to html5 --wrap=preserve --metadata=lang:en --css=$templates/style.css -Bnavbar   -o"
+for f in *
+do
+	[[ -d $item && -x $item/mkdocs.sh ]] && $item/mkdocs.sh
+	if [[ $f =~ (.*)".md"$ ]];then
+     	base=${BASH_REMATCH[1]}
+ 		if [[ $f -nt $destdir$base.html ]];	then
+ 			katex=""
+   			line=""
+    		for i in 1 2 3 4 5 6
+   			do
+	 			read line
+
+	 			if [[ $line =~ katex ]];then
+		 			katex=" --katex="$docroot
+	 			fi
+   			done <$f
+ 			pandoc  --variable $banner_height --variable docroot:$docroot --template $templates/pandoc.template $katex $options $destdir$base.html $base.md
+   			echo "$destdir$base.html from $f"
+		#else
+ 			#  echo "       $base.html up to date"
+		fi
+	fi
+done

docs/manifesto/motivation.md

@@ -18,7 +18,7 @@ It is possible to have a crypto currency similar to bitcoin where though there i
 
 A crypto currency needs to be centerless – it needs to able to survive the seizure of key servers by a hostile powerful party.  Trouble with bitcoin is that it is not centerless – proof of work winds up being centralized in a small number of extremely powerful and extremely expensive computers.
 
-Thus we need a system with proof of share, and not only proof of share, but proof of client stake – the power over the system needs to reside with peers that have a lot of wealthy clients – and it needs to be hard to find who the clients are, and where they are keeping their secrets, so that even if someone seizes important peers on charges of tax evasion and money laundering, does not thereby gain control.
+Thus we need a system with proof of share, and not only proof of share, but proof of client share – the power over the system needs to reside with peers that have a lot of wealthy clients – and it needs to be hard to find who the clients are, and where they are keeping their secrets, so that even if someone seizes important peers on charges of tax evasion and money laundering, does not thereby gain control.
 
 If the system handles an enormous number of transactions, peers are going to be big and expensive, thus vulnerable to people armed with vague and open ended charges of tax evasion and money laundering. Hence the power of peer over the currency needs to be proportional to the wealth controlled by the secrets held by that peer’s clients. And that peer’s clients need to be free to move from one peer to the next, and apt to move to peers that make it difficult for Mueller to find their clients.
 

docs/manifesto/navbar

@@ -0,0 +1,7 @@
+<div class="button-bar">
+  <a href="vision.html">vision</a>
+  <a href="scalability.html">scalability</a>
+  <a href="social_networking.html">social networking</a>
+  <a href="Revelation.html">revelation</a>
+</div>
+  

docs/manifesto/scalability.md

@@ -1,4 +1,5 @@
 ---
+# katex
 title: >-
 	Scalable and private blockchain
 sidebar: true
@@ -283,7 +284,8 @@ blocks into a higher level summary block, their chain and tree
 edges are discarded, because pointing to data that the reliable
 broadcast channel will no longer carry, and the newly created
 summary block gets a chain edge pointing to the previous summary
-block at the same level, and tree edge pointing to the previous higher level summary block.
+block at the same level, and tree edge pointing to the previous
+higher level summary block.
 
 We have to keep the tree around, because in order to register a
 commit for an output in the blockchain, we have to prove no
@@ -298,7 +300,28 @@ person as controls the wallet, will need to know the inputs to the
 transaction, and could sell that information to interested parties,
 who may not necessarily like the owner of the client wallet very
 much.  But the peer will not know the value of the transaction
-inputs or outputs, nor the what the transaction is about.
+inputs, nor what the transaction is about.  It will
+only know the hashes of the inputs, and does not even need to
+know the hashes of the outputs, though if the client wallet
+uses the same peer to register the change output, the peer will
+probably be able to reliably guess that that output hash 
+comes from that transaction, and therefore from those inputs.
+If Bob is paying Ann, neither Bob's peer nor Ann's peer knows
+that Bob is paying Ann.  If Bob is paying Ann, and gets a proof
+his transaction is valid from his peer, and he registers his
+change coin through his peer, and Ann registers her payment
+coin through her peer, his peer has no idea what the hash of
+that payment output was, and Ann's peer therefore has no way
+of knowing where it came from.
+
+Instead of obfuscating the data on public broadcast channel
+with clever cryptography that wastes a a great deal of space,
+as Monero does, we just do not make it public in the first place,
+resulting in an immense reduction in the storage space required
+for the blockchain, a very large reduction in the bandwidth,
+and a very large reduction of the load on peers.  They do not
+have download and validate every single transaction, which
+validation is quite costly, and more costly with Monero than Bitcoin.
 
 Once all the necessary commits have been registered on the
 reliable broadcast channel, only the client wallets of the parties to
@@ -307,7 +330,7 @@ that transaction that the transaction is valid. They do not need to
 publish on the reliable broadcast channel what transaction that
 was, and what the inputs to that transaction were.
 
-So we end up with the blockchain only carrying order $\log(h)$
+So we end up with the blockchain carrying only $\bigcirc\big(\log(h)\big)$
 blocks where $h$ is the block height, and all these blocks are likely
 to be of roughly comparable sizes to a single base level block.
 So, a blockchain with as many transactions as bitcoin, that has

docs/manifesto/social_networking.md

@@ -2,6 +2,8 @@
 # katex
 title: >-
 	Social networking
+sidebar: true
+notmine: false
 ...
 # the crisis of censorship
 
@@ -26,23 +28,35 @@ protocol, in order that you can have transaction metadata protected, and
 thus needs its own truth and reality system. And thus it needs to be willing
 to be at war with the Global American Empire. Its developers need to
 figure on a significant probability of being arrested, murdered or forced to
-flee, as Satoshi figured.
+flee, as Satoshi figured, though their inability to think beyond next weeks
+power point bullet points, and inability to comprehend the nature of
+cryptographic protocols will likely protect us.  On the other hand,
+the recent arrests of people who created privacy software for Ethereum
+suggests some risk.  I would never have tried what Tornado tried,
+for Ethereum is full of enemies who have longer time horizons
+and better capability to understand what we are up to than most of them,
+and Tornado was on the enemy's home turf.  You can get away with that
+stuff in the Bitcoin ecology so far, but no need to tread on the
+enemy's toes unnecessarily.  It draws unwelcome attention and forces
+them to think.
 
 We need a pseudonymous social network on which it is possible to safely
 discuss forbidden topics.
 
+## shills, spamming, and scamming
+
 We also have a crisis of shills, spamming, and scamming.
 
 [lengthy battleground report]:
-images/anon_report_from_people_who_tried_to_keep_unmoderated_discussion_viable.webp
+../images/anon_report_from_people_who_tried_to_keep_unmoderated_discussion_viable.webp
 "anon report_from people who tried to keep unmoderated discussion viable"
 {target="_blank"}
 
-Here is a [lengthy battleground report] from some people who were on the front lines in that battle, and stuck it out a good deal longer than I did.
+Here is a [lengthy battleground report] from some people who were on the
+front lines in that battle, and stuck it out a good deal longer than I did.
 
-  So we need
+So we need moderation.
-moderation.  But to prevent censorship, we need entirely decentralized
+But to prevent censorship, we need entirely decentralized moderation.
-moderation.
 
 People escape censorship to unmoderated anonymous platforms, but are
 driven off those platforms by shills, spammers, and scammers.

docs/mkdocs.sh

@@ -1,15 +1,11 @@
 #!/bin/bash
 set -e
-echo `dirname $0`
 cd `dirname $0`
+echo `dirname $0`
+for item in *; do
+    [[ -d $item && -f $item/mkdocs.sh ]] && $item/mkdocs.sh
+done
+echo all subdirectories done
 docroot="./"
 templates=$docroot"pandoc_templates"
 . $templates"/mkdocs.cfg"
-
-libraries/mkdocs.sh
-
-names/mkdocs.sh
-
-setup/mkdocs.sh
-
-rootDocs/mkdocs.sh

docs/names/multisignature.md

@@ -218,18 +218,15 @@ do not get all of it, they can calculate the signature.
 
 # Threshold Signatures
 
-FROST is an algorithm that produces a regular schnorr signature, and allows a quite large number of unequal shares. 
+FROST is an algorithm that produces a regular schnorr signature, and allows
+a quite large number of unequal shares. 
 
 
 A threshold signature has the interesting feature that it is a randomness
 beacon. If there is one honest participant party to the signing it generates a
-random value unpredictable to all participants,  This has obvious utility in
+random value unpredictable to all participants
-selecting the witness set and leader in blockdag algorithms equivalent to
-Practical Byzantine Fault Tolerant Consensus, and in distributing discrete
-shares in a way that is fair and on average over time approximates
-continuous stake as closely as possible
 
-The participants sign off on assertion that their stake is such and such, and
+One application:  The participants sign off on assertion that their share is such and such, and
 the signature itself controls the random distribution of fractional voting
 shares in the next signature as whole shares, so that voting shares, as
 nearly as possible, approximate ownership shares.

docs/pandoc_templates/mkdocs.cfg

@@ -7,30 +7,24 @@ elif [[ "$OSTYPE" == "cygwin" ]]; then
 elif [[ "$OSTYPE" == "msys" ]]; then
 		osoptions="--fail-if-warnings  --eol=lf "
 fi
-options=$osoptions"--toc --number-sections --toc-depth=5 --from markdown+smart+raw_html+native_divs+native_spans+fenced_divs+bracketed_spans --to html5 --wrap=preserve --metadata=lang:en  --include-in-header=icon.pandoc --include-before-body=$templates/before.pandoc --css=$templates/style.css -o"
+options=$osoptions"--toc --number-sections --toc-depth=5 --from markdown+smart+raw_html+native_divs+native_spans+fenced_divs+bracketed_spans --to html5 --wrap=preserve --metadata=lang:en  --include-in-header=icon.pandoc --css=$templates/style.css -o"
 for f in *.md
 do
  len=${#f}
  base=${f:0:($len-3)}
  if [ $f -nt $destdir$base.html ];
  then
-   katex=""
+	line=""
-   line=""
+	for i in 1 2 3 4 5 6
-   mine="--include-after-body=$templates/after.pandoc "
+	do
-   for i in 1 2 3 4 5 6
+		read line
-   do
+		if [[ $line =~ katex$ ]];
-	 read line
+		then
-	 if [[ $line =~ katex$ ]];
+			katex=" --katex=./"
-	 then
+	 	fi
-		 katex=" --katex=./"
+	done <$f
-	 fi
+	pandoc $katex $options $destdir$base.html $base.md
-if [[ $line =~ notmine ]];
+	echo "$base.html from $f"
-	 then
-		mine=" "
-	 fi
-   done <$f
-   pandoc $katex $mine $options $destdir$base.html $base.md
-   echo "$base.html from $f"
 
  #else
  #  echo "       $base.html up to date"

docs/pandoc_templates/pandoc.template

@@ -47,10 +47,12 @@ $endif$
 </head>
 <body>
 <div class="logo-header">
+  <a href="$docroot$/manifesto/motivation.html">
     <img src="$docroot$pandoc_templates/logo.svg" id="logo-graphic" alt="logo">
     <div style="height:18px;"></div>
     <div id="Rhocoin"></div>
-  </div>
+  </a>
+</div>
 $for(include-before)$
 $include-before$
 $endfor$

docs/program/mkdocs.sh

@@ -1,39 +0,0 @@
-#!/bin/bash
-set -e
-cd `dirname $0`
-docroot="../"
-templates=$docroot"pandoc_templates"
-echo $templates
-if [[ "$OSTYPE" == "linux-gnu"* ]]; then
-		osoptions=""
-elif [[ "$OSTYPE" == "darwin"* ]]; then
-		osoptions=""
-elif [[ "$OSTYPE" == "cygwin" ]]; then
-		osoptions="--fail-if-warnings  --eol=lf "
-elif [[ "$OSTYPE" == "msys" ]]; then
-		osoptions="--fail-if-warnings  --eol=lf "
-fi
-options=$osoptions"--toc --number-sections --toc-depth=5 --from markdown+smart+raw_html+fenced_divs+bracketed_spans --to html5 --wrap=preserve --metadata=lang:en --css=$templates/style.css -Bnavbar   -o"
-for f in *.md
-do
- len=${#f}
- base=${f:0:($len-3)}
- if [[ $f -nt $destdir$base.html ]];
- then
-   katex=""
-   line=""
-     for i in 1 2 3 4 5 6
-   do
-	 read line
-	 if [[ $line =~ katex$ ]];
-	 then
-		 katex=" --katex=./"
-	 fi
-   done <$f
-   pandoc  --variable banner_height:15ex --variable docroot:$docroot --template $templates/pandoc.template $katex $options $destdir$base.html $base.md
-   echo "$base.html from $f"
-
- #else
- #  echo "       $base.html up to date"
- fi
-done

docs/program/navbar

@@ -1,5 +0,0 @@
-<div class="button-bar">
-    <button>Button 1</button>
-    <a href="file:///C:/Users/john/src/reactionId/wallet/docs/writing_and_editing_documentation.html">writing</a>
-  </div>
-