In other words, this will be a long slog where most of the work is product-oriented and feature Xerox'ing, and not whiz-bang cool encryption oriented. Good luck :)
In other words, this will be a long slog where most of the work is product-oriented and feature Xerox'ing, and not whiz-bang cool encryption oriented. Good luck :)
How will they be distributed and replaced?
Who will generate them?
How will they get on my phone?
What happens when my phone is stolen?
How will they get to the people who want to communicate with me?
Hacking out a local client usable by unix nerds punts on these problems, more or less. Solve these problems in a way that fits into the workflow of present day average e-mail users (ie, my mom) and you will have something.
I do. Am I the only one who finds web-based email clients insufferably slow?
What if your standalone client is a website running on your local box with an interface similar to gmail?
> In other words, this will be a long slog where most of the work is product-oriented and feature Xerox'ing, and not whiz-bang cool encryption oriented.
Yes, you're right. The crypto itself isn't that complicated.