Option to change the hardcoded NickServ auto-join timeout value #221
Comments
- Added UI component to ServerDialog.nib - Added config save/load logic for the timeout param - Removed NICKSERV_INTERVAL constant Fixes psychs#221
|
👍 |
|
I could´t find this feature in released 2.42 version - how could I enable it? |
|
Same, how can we enable it in 2.42 or update to the repo version? |
|
@controlcde @wlkns The actual PR was never merged (#222). Some conflicts have been introduced since it was created, and I'm not really looking to maintain a fork. So my suggestion would be to look at the commit directly (cb6d22a), and apply the changes to your own fork. Sorry if I couldn't be of much help. |
|
Super lame... I read that LimeChat was highly configurable but I don't even have the basic features needed to simply maintain persistent connections to various servers and channels. Seems like that ability should be built in by design. Nobody anywhere ever wants to be automatically and permanently logged off when they lose their Internet connection. It shouldn't take a bunch of different settings (some of which don't exist, apparently) to "hack a solution into existence". Users get dragged through this long painful BS of trying to get a good setup, only to find out somewhere down the line that the software lacks the simple functionality. I'm guessing it's only Mac users like myself using it, since there are so many vastly superior IRC clients on every other platform. On to IRC client #4, I guess... |
|
And yet I have the exact opposite situation where auto-join spamming is causing me to be banned from channels. |
This ticket is to keep track of a PR which will add the ability to override the internal NickServ auto-join timeout. This is specially useful when dealing with slow networks and/or channels which have the
+rflag turned on, as stated in the following ticket: #12I will be changing the value from the default
5seconds, to15seconds; and it can be overridden through theServer Propertiesdialog window. See the following screenshot:The text was updated successfully, but these errors were encountered: