So Morphis is both a distributed data store and the ultimate solution to human suffering?<p>"MORPHiS is a global encrypted distributed datastore"<p>...<p>"It's about all of us, working together to create the world we want to live in, free from corruption, slavery, evil and manipulation; a vision many have thought impossible, until now."<p>I'd love to try out Morphis' anti-corruption and anti-manipulation features. Is there an API for these?<p>Seriously though, the project sounds interesting. It's cool to have a grandiose vision like this, but as the reader, I just don't see how it relates back to the project.
For those looking for a more practical decentralized storage solution that you can use to build apps with <i>today</i>, take a look at remoteStorage:<p><a href="https://remotestorage.io/" rel="nofollow">https://remotestorage.io/</a><p>The client-side library acts as an abstraction layer for multiple storage backends, including DropBox, Google Drive, and remoteStorage servers, and handles client-side sync, caching and persistence for you.<p>The remoteStorage server has multiple implementations that anyone can host and is based on an open spec.<p>I don't think it handles encryption though, but it really should. Its mission is to allow users to "own their data", and that won't ever be true as long as storage providers can freely inspect and copy data belonging to their users. Hopefully that's something on the roadmap.
I appreciate your enthusiasm and agree that your stated goals are important. But if you are serious about this project having an impact, you may want to get some feedback and help with the voice of your presentation. You talk of saving the world, but you are mainly talking about "you" saving the world. It comes across as grandiose ... Please speak clearly about your project and its specifics and less about you if you want people to listen.
Inspiring web page, but where does a user start? I can download, install, run, and then? You are missing some instructions about an interface.<p>Edit: Ok I looked harder. The RUNNING file has the critical protocol/port combination (<a href="http://localhost:4251" rel="nofollow">http://localhost:4251</a>) but this could also (or rather) be in the README, and on the web page.