Quote from: freigeist on September 06, 2017, 07:55:10 AM

Quote from: proemtheus on September 04, 2017, 01:54:47 PM

From what I have looked around Proemtheus is the first team to propose an independent email.
For our team to have an independent email means:
- decentralized accounts
- keep all user data private
It also means that even if Proemtheus will cease to exist you can use our software to have an active email account.

Proemtheus will not be a platform in the way you are calling it, meaning it will NOT be a closed system, but rather a different email that works seamlessly with the current email but in the meantime offer unique features.

In the case of email the existing system simply cannot be changed/improved because this will mean to cut off all free service offering companies from the pool of user data you know as profile. From exploiting this resource they make profits.

Hope I have address all your comments

Hello.

Thanks for your answer you addressed almost all the comments.
That is nice to hear you plan to implement an open system.

My question was related about reuse of existing codebase of other projects or other similar project or collaboration
with developers that aim to decentralize services.

I have seen your latest post in the thread and it speak about "Mailinabox".
https://bitcointalk.org/index.php?topic=2098671.msg21550317#msg21550317
I have never heard of it until now.

The question is could you reuse this code and build on top of that your email client or collaborate with the developer of that system
or you plan to build the client from zero?

Also when it comes to email storage how your email clients will store the data ?
Can it use existing decentralized platforms / projects like Sia, Stor-J , datacoin, Burst to store data
or maybe integrate one of those existing applications:
https://prism-break.org/en/all/#file-storage-sync

specifically this one: https://tahoe-lafs.org/trac/tahoe-lafs

or you have to build this also from 0 as well?

If so what would be the reasons to build the system from 0 and not reuse the existing code?!

Short answer: in regards to the email, client and server, we plan to build all software from zero.
Because most of the time writing fresh code is easyer than debugging / modifying / adapting ;-)
And also it's better to have alternatives.
Our email software will advise you to store data on the your devices. Preferably.
But you will be also able to use any storage solution you wish (decentralized or not).

Regarding the distributed storage we believe in a slightly different approach.
Proemtheus will create a network from the user personal devices in order to backup or retrieve to and from any of them. This means storage space available on all user devices will be unified.
There will be the option for public sharing / renting of space, but based on a score system maintained by reviewers.

The main problem with decentralized cloud (using storage rented from other users) is that a user renting space has its same information stored on more than one location, in case the storage-user is not online.
For example user information is stored on 10 other devices. But if no. 7 is not online you cannot retrieve that piece and therefor use your whole data set. So the system needs to multiply no. 7, and in fact all the other devices, by a factor depending on the storage-user online availability. The user depends on the slowest moving piece of his data. This multiplying of data translates in huge redundancy aka waste of space and bandwidth.

So we think it's best to build the storage also from zero as you can see we think a bit differently.
Thank you