Use cases exist in which you need to communicate securely and authenticated, but can NOT leak the above.
Some combination of Pond( message inboxes, timestamp randomization ) and Ricochet( authentication, origin/destination obfuscation ) is sorely needed.
Sounds like email in general is not the transmission medium you want then.
I think we're at a point where any long messages sent via the internet are going to be called "email" regardless of the actual transmission process. Especially if they aren't meant to be some kind of real-time chat system, as that is usually called "instant messaging".
> Tutanota is the end-to-end encrypted mail client that enables you to communicate securely with anyone.
Secondly: no. Twitter dm's are unlimited in length, and no one calls it email. Web based conversational systems offer long form messages, and people don't call them email.
Email is email, other things are other things. Something can be "email like" and not be email, and if explained that way even the most novice of users can understand that there is a difference, even if they themselves don't specifically understand what the difference is.
Also, please don't use all caps for emphasis. That's in the site guidelines: https://news.ycombinator.com/newsguidelines.html
The "yet another" is simply because the major points the authors themselves claim, are exactly the same as previous things (also submitted to HN) and with exactly the same fundamental problem, which I specifically described, and even suggested an alternative approach to.
I understand that you want to encourage positive feedback, but I have to ask: are you saying my wording needs improvement (i.e. I should have said "this has the same problem as other similar projects, X, y, z") or are you saying negative feedback in general is discouraged?
The most important place to be careful about this is in discussing new work. That of course doesn't mean that all new work is good, but the bias toward tearing things down is so strong (especially on the internet) that it's better to err on the other side.
There are already two, count them, TWO, existing, open, well-understood ways to both sign and encrypt email between two parties: PGP, and S/MIME.
Currently, the UX around setting up and using each of these tools is.. less than stellar.
Now. Just go with me here. What if all the people who keep claiming to have "solved the encryption problem" by locking everyone into their own little silo, instead of doing that, WORKED ON SOLVING THE USABILITY PROBLEMS?