[Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] #328

Open
incognico opened this Issue Apr 23, 2013 · 6 comments

6 participants

@incognico

It is a matter of taste but I think having *status NOTICE is less annoying, for example in this case:

06:43 <status> IRC connection timed out. Reconnecting...
06:43 <
status> Disconnected from IRC. Reconnecting...
06:44 <status> IRC connection timed out. Reconnecting...
06:46 <
status> IRC connection timed out. Reconnecting...
06:48 <status> IRC connection timed out. Reconnecting...
06:50 <
status> IRC connection timed out. Reconnecting...
06:51 <status> Connected!
06:53 <
status> The channel #xy could not be joined, disabling it.

Sometimes NOTICE is used already, in this case parting #xy:
11:43 -*status(znc@znc.in)- Removing channel [#xy]

My wish: Let the user choose if he wants to get PRIVMSG'd or NOTICE'd

There is a $5 open bounty on this issue. Add to the bounty at Bountysource.

@teward

If you don't mind my opinion, I don't think this is a bright idea. A problem I routinely see with IRC clients is that they don't show notices all on one screen. By using a PRIVMSG it will open a window with *status and all messages will be seen, rather than notices sometimes getting missed because they don't always get dumped into a "notices" window, and sometimes only show up on the active tab/channel/window.

@Mikaela

See http://tools.ietf.org/html/rfc1459.html#section-4.4.2

4.4.2 Notice

      Command: NOTICE
   Parameters: <nickname> <text>

   The NOTICE message is used similarly to PRIVMSG.  The difference
   between NOTICE and PRIVMSG is that automatic replies must never be
   sent in response to a NOTICE message.  This rule applies to servers
   too - they must not send any error reply back to the client on
   receipt of a notice.  The object of this rule is to avoid loops
   between a client automatically sending something in response to
   something it received.  This is typically used by automatons (clients
   with either an AI or other interactive program controlling their
   actions) which are always seen to be replying lest they end up in a
   loop with another automaton.

   See PRIVMSG for more details on replies and examples.
@incognico incognico changed the title from [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG to [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] Jun 23, 2014
@znc-bountysource znc-bountysource changed the title from [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] to [$5] Nov 26, 2014
@DarthGandalf DarthGandalf changed the title from [$5] to [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] Dec 2, 2014
@DarthGandalf DarthGandalf referenced this issue in bountysource/core Dec 4, 2014
Closed

Github plugin not working as expected. #932

@incognico incognico changed the title from [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] to [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG Jan 19, 2015
@incognico

@teward that depends on the client and its configuration, I don't think this is a valid concern, especially not if PRIVMSG/NOTICE is toggleable as an option in ZNC and you default to PRIVMSG (even if it would be wrong to do (at least in the case of the lines I have posted in op), see @Mikaela's post).

@znc-bountysource znc-bountysource changed the title from [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG to [Feature Request] Option to make ZNC/*status NOTICE instead of PRIVMSG [$5] Feb 21, 2015
@jpnurmi
znc member

👍

I'd also prefer such messages as "Connected!" as notices, instead of opening a new *status query window.

@jpnurmi jpnurmi added a commit to jpnurmi/znc that referenced this issue Sep 2, 2015
@jpnurmi jpnurmi Turn most status messages to notices instead (#328) ab29394
@jpnurmi jpnurmi added a commit to jpnurmi/znc that referenced this issue Sep 26, 2015
@jpnurmi jpnurmi Turn most status messages to notices instead (#328) a5fc176
@jpnurmi jpnurmi added a commit to jpnurmi/znc that referenced this issue Sep 27, 2015
@jpnurmi jpnurmi Turn most status messages to notices instead (#328) fd3df78
@dreamcat4

+1

I'd also prefer such messages as "Connected!" as notices, instead of opening a new *status query window.

@dreamcat4

Hi. In the meantime I have a suggested a workaround for weechat client, which is being proposed in the form of a bug fix, on an existing feature of weechat/buffers.pl

weechat/scripts#146

Unfortunately it seems the script's author is being highly resistive to the idea of merging it ATM. Heres to hoping they will be a bit more sympathetic, and possibly change mind / make a concession. Its just a couple of lines of code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment