Ticket #1401 (reopened Defect)

Opened 3 years ago

Last modified 2 years ago

Query windows cannot send commands to znc

Reported by: narge Owned by: timothy
Priority: Normal Milestone:
Component: Colloquy (Mac) Version: 2.2 (Mac)
Severity: Normal Keywords:
Cc: narge-colloquy-bugs@…, mmitar@…

Description

The znc bouncer is controlled by sending messages to pseudo-users with nicks starting with *. For example, connections and the general state of the bouncer is controlled by privmsg to *status, and the auto-away plugin is controlled by sending messages to *away. However, znc passes watch commands directly to the real server, so colloquy will be told that these users are offline:

WATCH +*status
605: *status * * 0 is offline

As of colloquy 2.2, this makes it impossible to simply type a command in the *status query window; colloquy will display an error dialog. Instead, one must type /msg *status command.

This is arguably a bug in znc, but Colloquy's preemptive denial of messages typed in query windows is still annoying. Why are they not handled the same way as /msg commands? (ie, sent to the server, and then the error dialog shown if the server responds with a 401)

Change History

Changed 3 years ago by narge

  • cc narge-colloquy-bugs@… added

Changed 3 years ago by timothy

  • status changed from new to assigned

Thanks for the ticket. This is related to #1346.

Changed 3 years ago by zach

Related: #1414

Changed 2 years ago by zach

  • status changed from assigned to closed
  • resolution set to wontfix

*status isn't actually a user, so its not online.  http://en.znc.in/wiki/Fakeonline will fake the online status for *status. Colloquy can't really fix this, since *status can actually be *anything, defined by the user in ZNC's config.

Changed 2 years ago by mitar

  • cc mmitar@… added
  • status changed from closed to reopened
  • resolution wontfix deleted

Could at least this user-online-check "feature" be made configurable? Or at least it could still allow you to send a message, just it would warn you that user is probably offline and will not get a message. Like Adium does. It does not need to be configurable on per-nick basis. I would completely turn off this feature for me.

Note: See TracTickets for help on using tickets.