[Imported from Trac: page Summit2Day1, version 2]

Summit2Day1.md

@@ -52,7 +52,10 @@ expected vs required vs known, k-of-N, H, points, understandability
     - Brian says client/gateway should expect user to teach it what sort of
       grid they expect, so it can bail when expectations aren't met
     - Shawn would prefer scheme where client measures reliability itself,
-      chooses k/N/H to meet certain speed/cost/reliability goals
+      sets N to the number of servers currently accepting shares, sets H
+      slightly below N (to improve upload availability) and computes and
+      uses a k that maximizes performance (or minimizes cost) while achieving
+      a target reliability.
 
 ## encrypted git, or revision control on tahoe
     - Zack(?) is thinking about revision control on top of Tahoe, will