I tried beta web wallet. Seems to be working, incredibly fast and smooth. But with real transaction fees sending cryptsi will be much less fun

questions:

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

2. web wallet should be https

I just want to laugh out loud, I want to look at investors lose money.

1. We can't, because in this way we need to store your passphrase in cookie browser. It's dangerous. Every transaction need sign.
2. Yes, we will add SSL today.

3. About fees read first post. Fees decreases with each increasing amounts volume

Localstorage dangerous too, all you passphrases will be stored in your browser.
Passphrase create public and private key. We can try to save passphrase in memory, then create something like session.
But we need to see how far it is safe.

What do you mean, what about the raised BTC in bter until now, is there any bonus? I have been following this thread and know it had started from the posts this morning.

LocalStorage is replacement for Cookie. It's not safe. You can read the content of localStorage by using third-party local program or manual using browser tools.
Can you tell exactly how Ripple uses the localStorage?

It won't be possible, as the raised funds will be controlled by the Foundation, who will spend the funds on development, marketing and promotion. We all prefer to have Crypti reach leading status organically, rather then via manipulations.

The point of using localStorage and public key cryptography is to mitigate against MITM and replay attacks, cookie/session jacking, and keep the application stateless.

The "third-party local program" argument is invalid because a malicious third party local program can read a passphrase input in to a web page also.

I think code examples are already open source, or you can just go to the ripple client and look at the code. Many other things use this method too, it is proven.

Not all.

ok, why don't have topic in russian language?