[tahoe-dev] [tahoe-lafs] #573: Allow client to control which storage servers receive shares

[tahoe-lafs]

#573: Allow client to control which storage servers receive shares
--------------------------------+-------------------------------------------
 Reporter:  swillden            |           Owner:           
     Type:  enhancement         |          Status:  new      
 Priority:  minor               |       Milestone:  undecided
Component:  code-peerselection  |         Version:  1.2.0    
 Keywords:                      |   Launchpad_bug:           
--------------------------------+-------------------------------------------

Comment(by zooko):

 Brian has implemented much of this, but it isn't commented-in, documented,
 etc. in the current trunk.  The next step (after the Tahoe v1.5.0 release)
 is to experiment with use cases and UI.  Anybody out there want to
 actually use this for something?  Shawn Willden has mentioned that he
 wants to make sure his mom's PC gets {{{K}}} shares.  Jake Appelbaum has
 mentioned that he wants to make sure non-Tor-hidden-server nodes get
 {{{N-K}}} shares.  Some corporations have mentioned that they would like
 to send approximately the same number of shares to each of {{{Q}}}
 different geographically distributed data centers.

 I think we need some brave user like Shawn or Jake to try this feature out
 and complain about how it doesn't do what he wants.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/573#comment:3>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid