diff --git a/docs/manifesto/social_networking.md b/docs/manifesto/social_networking.md
index b371f6f..1506be2 100644
--- a/docs/manifesto/social_networking.md
+++ b/docs/manifesto/social_networking.md
@@ -161,8 +161,13 @@ without the substance of a real conversation. And the same was happening
 in every Usenet group, though what was being shilled varied from one
 group to the next, with an immense multitude of different shilling
 organizations running an immense multitude of unresponsive scripts
-promoting an immense multitude of different scams, most of them about
-money rather than politics.
+promoting an immense multitude of different scams, initially
+most of them about money rather than politics, but what killed usenet
+was political shills.  
+In the 3rd Reich there were no chess clubs or sewing circles only
+national socialist chess clubs and sewing circles. Clownworld has
+adopted the policy that there be only progressive and gay chess
+clubs and dykey and progressive sewing circles.
 
 Two real participants in the science fiction and fantasy Usenet group would
 be having a conversation about the hero’s journey, and the computer of
@@ -473,14 +478,16 @@ Kademlia the $log_2$  of the exclusive-or between his hash and your hash.
  that are closest to the target.  And then you connect to those, and ask the
  same question again.
 
+ This works if each computer has approximately the same number of connections 
+ close to it by a metric as distant from it by some metric.  So it will be
+ connected to almost all of the computers that are nearby to it by that metric.
+
  In the course of this operation, you acquire more and more active
  connections, which you purge from time to time to keep the total number
- of connections reasonable, the distribution approximately uniform, the
- connections preferentially to computers with long lived network addresses
- and open ports, and  connections that are distant from you distant from
- each other.
-
- The reason that the Kademlia distributed hash table cannot work in the
+ of connections reasonable and the distribution approximately uniform by the
+ metric of distance used.
+ 
+  The reason that the Kademlia distributed hash table cannot work in the
  face of enemy action, is that the shills who want to prevent something
  from being found create a hundred entries with a hash close to their target
  by Kademlia distance, and then when your search brings you close to
@@ -497,10 +504,8 @@ response to that thread to  a public repository, they did the equivalent of a
 git commit and push to that repository.
 
 Each repository contains all the material the poster has approved, resulting
-in considerable duplication, but not enormous duplication.
-
-
- approved links and reply-to links – but not every spammer, scammer, and
+in considerable duplication, but not enormous duplication, approved links and
+reply-to links – but not every spammer, scammer, and
  shill in the world can fill your feed with garbage.
 
 
@@ -813,7 +818,8 @@ To provide a reliable broadcast channel, a hash of the total state of the room i
 
 # signing and immutability
 
-For money, we want signatures, and money is the highest priority.   Carol
+For money, we want signatures, and money is the highest priority.
+Information wants to be free, but programmers want to be paid.  Carol
 signs what she said to Bob, and she is stuck with it. Less cases to handle.
 When you send money, you not only sign it, thus rendering it immutable
 but deletable, you sign the message, thus signing all the previously
@@ -1083,6 +1089,21 @@ pressure.  We start by enabling discussion groups, which will be an
 unprofitable exercise, but the big money is in enabling business.
 Discussion groups are a necessary first step.
 
+## Cold Start Problem and Metcalf's law.
+
+The value of joining a network depends on the number of other people already using that network.
+
+So if there are big competing networks, no one wants to join the new network.
+No one is going to want to be the first to start a Sovcorp.  And until people do,
+programmers are not going to get paid except by angel investors expecting that
+people will start Sovcorps. So to get a foot in the door, we have to cherry pick
+and snipe little areas where the big network is failing, and once we have a foot
+in the door, then we can get rolling.
+
+### Bitmessage
+
+The lowest hanging fruit of all, (because, unfortunately, there is no money or prospect for money in it) is to replace Bitmessage.
+
 # Development sequence
 
 First we need a replacement for Quic, TCP, and SSL.  Quic and SSL encryption
diff --git a/libsodium b/libsodium
index 914033d..b6e1e94 160000
--- a/libsodium
+++ b/libsodium
@@ -1 +1 @@
-Subproject commit 914033d2c70831b86e94a25f27e61a94bc7d45c8
+Subproject commit b6e1e94cfb3d8dffdb1bb92b6102e5fad5fe6093