Bug #868


Don't write broadcast/PMs in logs of unrelated channels

Added by Infinity Zero 3987 days ago. Updated 3340 days ago.

Status:Closed Start:08/12/2013
Priority:Normal Due date:
Assigned to:avatarMirco Bauer % Done:


Category:Engine IRC
Target version:1.0


Found in Version:

Votes: 4 (View)


At the moment, broadcast notices such as the below are displayed in some channel windows1, to make the notice obvious.

23:04:40 -ChanServ (ChanServ@services.)- [#gnu] Welcome to #gnu, the official channel of the GNU Project. Please read and follow http://www.gnu.org/server/irc-rules.html. 

However these show up in logs too. This is unnecessary, being redundant and irrelevant, and makes the logs potentially confusing.

In fact I would go as far to not display these messages in unrelated channels at all; instead display them in the server channel window and set a highlight for the user.

[1] I can't work out how smuxi chooses which channels to display this message in; it's less than "all channels" but greater than "the channel that's currently displayed".

Related issues

related to Smuxi - Feature #38 send notices from users to channels and querys where useful Closed
duplicated by Smuxi - Bug #1050 Entring channel notice in wrong channels Closed 05/02/2015

Associated revisions

Revision e4ced9a61f46b86a203c04d1058caf9fd5e7a201
Added by Mirco Bauer 3340 days ago

Engine-IRC: don't show notices on shared channels for Nick/ChanServ (closes: #868)

This "show notices on shared channels" feature was introduced in #38 but became
annoying with Nick/ChanServ which send channel welcome messages or other
replies which then got spammed to all channels.


Updated by Mirco Bauer 3981 days ago

  • Category set to Engine IRC
- Notices from users you share channels with will also be shown on the
channel and the server tab to make it easier to see their notices.
(closes: #38)

Services are a special case I guess and are indeed a bit annoying. Smuxi should try to detect them (or hardcode some known nicks) and not do this. For the messages from services I agree.

Updated by Mirco Bauer 3724 days ago

  • Complexity set to Low

Updated by Jim C K Flaten 3644 days ago


It would be nice if we could configure where notices went. They currently go to all channels that you have in common with the sender, I believe, which gets pretty bad when communicating with network services. The options to route these messages should include at least:

  • Display in all common channels (current behavior).
  • If there is only one channel in common, display in that channel.
  • Display in currently selected channel.
  • Display only in the server tab.

Some people might prefer a mix of these options, so perhaps allowing multiple of them to be selected would be good. To make it even more complex, this could be implemented as a set of rules, where you always have a default rule, but can add new ones that change the behavior of a specific server or user.

| Rule name | Network | Source             | Common | Single | Active | Server |
| Default   | *       | *                  | X      |        |        |        |
| Services  | *       | ChanServ, NickServ |        |        |        | X      |
| ...                                                                          |

Updated by Mirco Bauer 3347 days ago

  • Assigned to set to Mirco Bauer
  • Target version set to 1.0

I think for a quick fix NickServ@ and ChanServ@ should be blacklisted to be shown on "common/shared channels"

Updated by Mirco Bauer 3340 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF