This is a valid point -- yet we needed this to fulfill one of our primary goals -- respect privacy by not trusting servers. TimeGT is generating a private/publ

This is a valid point -- yet we needed this to fulfill one of our primary goals -- respect privacy by not trusting servers. TimeGT is generating a private/public keypair for users and information/dataset-changes at server are encrypted with that. It could provide password recovery feature but then users can't fully trust their privacy. One option is also that user keeps carrying public/private keypair file with a memory-stick but probably remembering password is easier? One of the problems with online tools like RememberTheMilk or GMail is that some people do not feel confident having information stored in servers readable for the company. To sum up, TimeGT is built on the idea to respect user privacy and is build up to not have a centrally available readable information storage. I think it's good to have a choice of not trusting your information to anyone but yourself, isn't it? :) We'll put it to the roadmap that user has the option to "enable password recovery" and in that case they just need to trust our server security, just like users who use rememberthemilk etc. Hopefully there will be more confirmation that password recovery is a serious limitation and this will can be solved without affecting users who want current strict security.