-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regular disconnect / reconnect #117
Comments
From what I've seen, these disconnects are initiated by slack itself -- the plugin tries hard to keep connections open. It might be theoretically possible for the plugin to handle reconnects itself, but it creates tricky windows where messages have to be queued somehow. As for suppressing the messages, those look like the connection steps (normally shown as a progress bar in pidgin), so that sounds like a bitlbee question. |
Ah I see. The main consequence of this though is that it seems to lose the reference for multi-user group DMs after a reconnect. (This may be a bitlbee issue too, I don't know) |
Just updating my previous comment, it seems as though all open chats (DMs, joined channels, etc) lose their identities after such a reconnect. A new message from anyone else in that chat re-establishes the connection, but until then, messages sent to that chat disappear into the aether. |
Same problem as op, triggers notifications everytime the reconnect triggers. be nice to see these handled |
Every ~8 hours, the plugin disconnects and reconnects, spamming my bitlbee control channel with the following messages:
Is there a way to diagnose (then prevent) these drops, or if not at least suppress these messages?
The text was updated successfully, but these errors were encountered: