Opened at 2012-05-17T17:26:42Z
Last modified at 2017-07-10T16:03:50Z
#961 new enhancement
otr autoconnect
| Reported by: | Owned by: | pesco | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OTR | Version: | 3.0.5 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
I find myself doing "otr reconnect" when messaging someone for the first time in a while. I still have to look wether they have reconnected their client. This is cumbersome.
What do you think about an option for bitlbee to automatically disconnect otr if the other client quits and (re-)connect when he (re-)joins? This would make OTR a lot easier to use.
Also it wouldn't give away when I OTR connect to whom, since I connect to everyone who's available.
Attachments (0)
Change History (3)
comment:1 Changed at 2014-02-07T16:29:31Z by
comment:2 Changed at 2015-11-11T11:27:35Z by
Is there any news on this topic? The mentioned behaviour is really annoying!
comment:3 Changed at 2017-07-10T16:03:50Z by
There seem to be quite a few problems with OTR support in bitlbee relating to desynchronized sessions (unexpected encrypted message received, unencrypted message received, etc). It seems as though an automatic session renegotiation happened in at least some of these situations once upon a time, but it stopped working, though I may be mistaken since there seem to be quite a lot of edge case situations involved.
Pidgin seems better at initiating renegotiation when an unexpected state is detected. It would be great if bitlbee tried harder to resynchronize in such events, instead of only displaying a warning message.
cf. comment:5:ticket:766