modules_online should intercept WATCH entries for module nicknames #281

New Issue

2026-10-05T04:09:47+02:00

adam commented

2026-10-05 04:09:47 +02:00

On Colloquy Mobile, query windows trigger a WATCH line. ZNC passes the watch command to the server which responds with offline status for nicks such as *status, and Colloquy will not allow sending messages via that window until it detects online status (either a PRIVMSG from that nickname or a WHOIS with modules_online loaded). It's a little inconvenient.

Can module_online intercept WATCH entries and respond with a 604 status for known ZNC nicknames?

Example watch response:

WATCH +*shell +*status +foo
605 foo *shell * * 0 is offline or empty
605 foo *status * * 0 is offline or empty
604 foo foo ~bar 96.XXX.XXX.XXX 0 is online or present

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1363035-modules_online-should-intercept-watch-entries-for-module-nicknames?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

On Colloquy Mobile, query windows trigger a WATCH line. ZNC passes the watch command to the server which responds with offline status for nicks such as *status, and Colloquy will not allow sending messages via that window until it detects online status (either a PRIVMSG from that nickname or a WHOIS with modules_online loaded). It's a little inconvenient. Can module_online intercept WATCH entries and respond with a 604 status for known ZNC nicknames? Example watch response: ``` WATCH +*shell +*status +foo 605 foo *shell * * 0 is offline or empty 605 foo *status * * 0 is offline or empty 604 foo foo ~bar 96.XXX.XXX.XXX 0 is online or present ``` ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1363035-modules_online-should-intercept-watch-entries-for-module-nicknames?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:09:48 +02:00

+1

+1

adam commented

2026-10-05 04:09:49 +02:00

Some clients also perform whois when queries are opened which I think this would help the most.

Colloquy will not allow sending messages via that window until it detects online status (either a PRIVMSG from that nickname or a WHOIS with modules_online loaded)

It should probably be mentioned that you cannot send messages to watch entries anyway as they don't exist and *status will tell you that there is no such module.

Some clients also perform whois when queries are opened which I think this would help the most. > Colloquy will not allow sending messages via that window until it detects online status (either a PRIVMSG from that nickname or a WHOIS with modules_online loaded) It should probably be mentioned that you cannot send messages to watch entries anyway as they don't exist and *status will tell you that there is no such module.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#281