Skip to content
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

Option to change the hardcoded NickServ auto-join timeout value #221

Open
rudisimo opened this issue Apr 10, 2014 · 6 comments · May be fixed by #222
Open

Option to change the hardcoded NickServ auto-join timeout value #221

rudisimo opened this issue Apr 10, 2014 · 6 comments · May be fixed by #222

Comments

@rudisimo
Copy link

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 +r flag turned on, as stated in the following ticket: #12

I will be changing the value from the default 5 seconds, to 15 seconds; and it can be overridden through the Server Properties dialog window. See the following screenshot:

Imgur

rudisimo added a commit to rudisimo/limechat that referenced this issue Apr 10, 2014
- Added UI component to ServerDialog.nib
- Added config save/load logic for the timeout param
- Removed NICKSERV_INTERVAL constant

Fixes psychs#221
@thedodd
Copy link

thedodd commented Sep 25, 2014

👍

@controlcde
Copy link

I could´t find this feature in released 2.42 version - how could I enable it?

@wlkns
Copy link

wlkns commented Oct 28, 2014

Same, how can we enable it in 2.42 or update to the repo version?

@rudisimo
Copy link
Author

@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.

@rrdein
Copy link

rrdein commented Aug 1, 2018

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...

@jhaenchen
Copy link

And yet I have the exact opposite situation where auto-join spamming is causing me to be banned from channels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants