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

getchanidle for $botnick is not reset on PRIVMSG in puthelp/serv/quick #816

wilkowy opened this issue Jun 24, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jun 24, 2019

Feature request. (currently for 1.8.4)

The getchanidle $botnick $chan does not return a valid idle (or should I say observed last activity) time when we query for a bot itself. The value is reset on some events like setting channel mode (pushmode or putkick), but it is not when sending normal messages to queues. Most likely because ordinary PRIVMSGs do not cause any feedback from IRC server.

Queue manager could parse text we send to server and reset bot's idle if valid PRIVMSG is detected as well. (and other omitted protocol commands which do not cause any feedback message, but might be observed on channel by others)

IMHO it does not really matter for a bot if server received and propagated further into the network those messages. (or it does…?)

For example .tcl puthelp "KICK #channel somenick :somereason" and .tcl putserv "MODE #channel +m" cause idle reset because server responds with [24/02:13:14] [@] botnick!ident@host MODE #channel +m so it is observed by bot and causes bot's event and hence an idle reset.

However this is not exactly correct as getchanidle is not really an idle, but observed last activity. For example pushmode does not reset IRC idle, but is considered as a reset by a bot (for any nick). This should have to be clarified in docs at least (or command renamed?).

(not sure about backward compatibility for scripts; this behaviour was observed for 1.6.21 as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.