In bitlbee after reconnection channels are recreated and not reused

[Aketzu]

I use telegram through bitlbee so I have all possible chats in single irssi window. One particularly annoying feature is that when telegram reconnects it loses existing chat windows and then I have to do magic to get them back where they were.

1) use normally, #realchannel is in irc-channel #realchannel 2) telegram reconnects, #realchannel shows netsplit 3) after a while bitlbee opens #chat_000 irc-channel for that #realchannel. Old window stays dead, new channel works. 4) if I close #realchannel in irc whole bitlbee segfaults 5) after bitlbee restart/reconnect+reauth telegram chat opens in original #realchannel

With other bitlbee chatnets (facebook, sipe, gtalk) window namings seem to work better although I don't do groupchats that much on others.

Any ideas whether this is telegram-purple related thing (some chat/window id differs from original) or bitlbee issue on window handling?

&bitlbee
06:51 <@root> telegram - Error: Lost connection to server...
06:51 <@root> telegram - Signing off..
06:51 <@root> telegram - Reconnecting in 5 seconds..
06:53 <@root> telegram - Login error: Connection timeout
06:53 <@root> telegram - Logging in: Signing off..
06:53 <@root> telegram - Logging in: Reconnecting in 15 seconds..
06:53 <@root> telegram - Logging in: Logged in

#realchannel
06:51 *** Netsplit kelvin.aketzu.net <-> telegram.kelvin.aketzu.net quits: User1, User2...  
          (+45 more, use /NETSPLIT to show all of them)

#chat_000
06:59:12 *** ServerMode/#chat_000 "+t" by kelvin.aketzu.net
06:59:12 *** Irssi: #chat_000: Total of 2 nicks (2 ops, 0 halfops, 0 voices, 0 normal)

[Aketzu]

Crossposted to https://bugs.bitlbee.org/bitlbee/ticket/1222 telegram-purple version latest git, 006890a

[dequis]

Crossposting my comment from the bitlbee trac because I didn't get a reply there:

I can't reproduce this. Using telegram-purple 1.2.2beta-1

When the account is disconnected, it leaves the channel saying "[Chatroom closed by server]", which >seems like it would make the rest impossible.

Also please try again with the latest git master, there are possibly relevant fixes.

(the latest git master of bitlbee, that is, but latest telegram-purple is fine too)

I think it's more likely that this is bitlbee's fault and this ticket can be closed.

[dequis]

I've closed the ticket on bitlbee's side due to inactivity and the fact that it works for everyone else.

You should probably close this one too.