| Ticket UUID: | 2c4e8ebcecb51c0cc85c6a4a782cbcec799b57bd | |||
| Title: | Auto-reconnect when connection is lost for long periods of time | |||
| Status: | Open | Type: | Feature_Request | |
| Severity: | Minor | Priority: | Low | |
| Subsystem: | Discord | Resolution: | Open | |
| Last Modified: | 2019-04-14 01:17:15 | |||
| Version Found In: | 0.3.7 | |||
Zero3K — 2018-12-31 04:32:52It would be nice if it could auto-reconnect when the connection is lost by continuously pinging a site (or do something that's not invasive) until the connection is restored, then connect to Discord and/or Slack. | ||||
cancel — 2018-12-31 04:37:57Yeah. Original ticket for this was migrated from the old todo system: [cbe8e19309]
Related: [ce77725f4f]
| ||||
cancel — 2019-01-20 06:14:25This is now implemented for Slack, but not Discord. Changing the subsystem tag to Discord until it's implemented there as well. | ||||
spinda — 2019-04-11 02:06:09Is this actually implemented for Slack? I can't find an option for it. Whenever I put my laptop to sleep and then wake it back up after a while, Slack ends up stuck in a disconnected state until I manually hit the "Connect" button. | ||||
|
cancel — 2019-04-12 08:48:52 Ripcord will give up trying to reconnect if it fails reconnecting too many times. There might be some issue on your system where your wifi takes too long to come online, and Ripcord gives up trying to reconnect. (It does have exponential back-off, but if your wifi takes longer than 45 seconds or so to come up, then I supposed it could still happen.) | ||||
|
spinda — 2019-04-12 22:32:19 Hmm, I see. Can we please have an option to prevent Ripcord from giving up, then? (Should I open a separate ticket for that?) | ||||
|
cancel — 2019-04-13 00:46:22 No, that option will not be created for Discord. If the reason it cannot connect is due to a Discord service problem, attempting to spam it with connections for a long period of time might get your account banned or something. | ||||
|
spinda — 2019-04-14 00:54:49 I meant for Slack, actually. | ||||
|
spinda — 2019-04-14 01:17:15 Also, according to my ripcord.log, Ripcord gives up trying to reconnect to Slack after ~16 seconds - example: https://0bin.net/paste/2sFwPWfAt44G21NB#YTN39g8p-cGEpHRwU+EUvMKFqTHLcjiMFXBKJ+i/TdM If reconnecting to a service fails, Ripcord could perhaps check whether the system has internet connectivity at all, by requesting a known URL like http://detectportal.firefox.com/success.txt (whose response should always be "success" if the connection is functional). If the system's connectivity is down, Ripcord could 'slumber' for a while, periodically checking for an internet connection, and then kick off reconnecting to Discord/Slack again once it's back up. This way, there wouldn't be a risk of accounts getting banned for making excessive requests to those services. | ||||