Sending emails using the new web interface now works using all the new parts, except it is still using the old RTS code. I still haven't updated the SMTP code so it doesn't work at the moment, but fixing that shouldn't be a lot of work. There is some work left before everything else works as it should, but I'm quite confident that I'll only be working on the UI stuff after midterm (except the RTS changes and a few bugs).
There is still a problem with the channels that needs fixing. If both Alice and Bob sends messages to each other at the same time they will end up using two different channels, so we need to resolve that conflict somehow. My first though was something like this: The receiver of an RTS first checks if it has a keypair for the channel already. If not there is no conflict to be resolved, so the values in the RTS are used for the new channel with the sender. If the recipient already has a keypair the two identity IDs are compared and the keypair of the identity with the lowest ID is used. The identity with the lowest ID must also resend the RTS in case Bob has deleted a previous channel he had with Alice and sends a new message to her (Alice has the lowest ID). However forcing one side to resend the RTS means having the user solve another captcha, in some cases just to receive messages, which is something I'd like to avoid. Any thoughts or other options? Some cases to consider: * Alice sends a message to Bob (no previous channel) * Both Alice and Bob tries to open a new channel at the same time * Alice sends a message to Bob, who knows of a previous channel that Alice has deleted -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20110705/d2bfe9f4/attachment.pgp>
