Improvements in OTR session handling

[nd2s]

There are several annoyances with the current OTR support. Here is a list of possible improvements (ordered from most to least important):

• When the connection to the server is lost the OTR session is lost as well. Profanity should automatically start OTR again. If I currently don't start the session again manually before my contact writes me, I will receive unreadable encrypted messages.
• When an encrypted message that can't be decrypted is received, Profanity should reestablish the OTR session immediately. Right now I often get a bunch of encrypted messages I can't read from Adium users without them even noticing. I then have to manually start OTR and asked them to copy their 10 or so last messages.
• When the contact's OTR policy is set to always, Profanity should try to establish an OTR session before sending a message instead of just printing the Failed to send message. OTR policy set to: always error message.

[nd2s]

Actually I just noticed that Gajim (the deprecated OTR plugin) seems to be able to request unreadable message to be resent.

‎[kl. 11.14 +0000] [OTR: The encrypted message received from user@domain.net/resource is unreadable, as you are not currently communicating privately]
‎[kl. 11.14 +0000] [resent] Bla bla this is the super secret message.

[jubalh]

I guess most people moved on to OX and OMEMO.
And it looks like some of the issues mentioned here are solves already.
#952 tracks another thing mentioned here.
Thus closing this.