It's not verbose enough

sloantothebone

It's just not verbose enough for me, I can hardly be certain it's working. Although I have nobody else who has OTR to test it with. Let me know if I need to be more specific.

keithdunnett

The same remark was made when I popped into ##otr (Freenode) and #otr (OFTC) to find someone to test it with - and was rapidly obliged, too. For me, the plugin in operation was clear enough and it duly put the explanations in the correct windows, though I'm broadly familiar with OTR. Where it perhaps might do well to be clearer is in the help text returned by /otr. Having thought to generate my keys first (by FQDN of server as suggested by the help text), a /otr start ignored these and generated new keys for nickname@Network instead. Suggests one could perhaps usefully document /otr genkey further, or leave key generation to /otr start. The actual OTR process seems to work fine to me, but the help text could perhaps be improved.

fred0r

I personally miss right now a response of the Plugin that the otr-session is 'finish'ed. During the 'init' there's a Message ....