>>4309
This x 100
>>3764
OP I'd say that the best way to do something like this is to have the user keep an encrypted file container not with their own information but with bits and pieces of everyone else's info a-la bittorrent. However, JS would not be the language to code something like this in. You'd be better off with C, C++, or even Erlang since you're going to be doing distributed computing. Might also want to peek at Pony because it uses object capabilities and actors. Some very powerful stuff under the hood.
I had a similar idea to yours. Its doable but it will ultimately fail if you do it in Javascript. The other user is right. Allowing some dick to upload info to your server is asking for trouble. Information has to be securely stored, tamper proof, and safely transmitted.
In summation: a distributed/P2P system that requires the user to upload his information is a good idea if its done properly. The user must not be able to edit his own info except through a secure web interface. The data itself MUST be encrypted. Otherwise you need a way to sandbox each user's code.
Maybe check out Google's Caja? Its a variant of Ecmascript that uses capabilities.