Quote from: FrictionlessCoin on April 24, 2014, 11:03:32 AM

Quote from: dirvine on April 24, 2014, 10:55:57 AM

Quote from: liondani on April 24, 2014, 08:33:45 AM

Quote from: paulsonnumismatics on April 23, 2014, 02:17:32 PM

Quote from: superresistant on April 22, 2014, 09:51:07 AM

MaidSafe will have access to your data any time, will be able to sell it and I think they will do as they are greedy as hell.

I know is feeding the troll, but just one hint: The data will be ENCRYPTED. So no selling or accesing. ENCRYPTED.

Jesus.

If someone encrypt something I suppose they can decrypt it also...
Encrypted for us the users... not for them... did I miss something?

The encryption is all handled client side and explained in the papers and in the code (encrypt library). It is a form of convergent encryption and chunking. The network cannot decrypt the data, neither could any human without the keys (barring of course some massive code error etc. like any system). The code is all open source and audited by many devs universities and other parties. You can take a look and see how we have done some of these things, it is pretty good we think.

The point of the whole thing is you are in control, you and the machine, no humans and no intermediaries. That is a more natural way to work and very scalable.

Can you comment how the data dispersion algorithm differs from Cleversafe?

Not really, I am not sure the source is available for that. I see they use FEC, we do not, instead we use replication, and we disperse data randomly across a DHT Address space with replication and failover techniques involving account synchronisation and an accumulator pattern.