crypted conversation not initiated after generating new key with /otr init

[lelutin]

When you use /otr init for the first time, it does what we'd expect: generate a new key.

However, once key creation is done and hexchat-otr says the key was completed successfully and loaded, an encrypted communication is not initialized.

A workaround is to use /otr init again but since the status of the otr session is not easy to see, one can very easily think that the conversation is safe right after the first time this command was used.

It would be better if a crypted communication was started right after key generation when using init (not genkey since this command is meant to only generate a key)

[petterreinholdtsen]

It would also be great if it was possible to see the otr status somewhere, to be able to discover if it is disabled for some reason.