954448 - A less obtrusive way to display NickServ/ChanServ IRC messages

Status: RESOLVED DUPLICATE of bug 954905

(Chat Core :: IRC, defect)

Description

[aleth [:aleth]]

*** Original post on bio 1013 at 2011-09-02 10:55:00 UTC ***

Unless an error has actually occurred, it would be better if NickServ/ChanServ messages (and e.g. the one you get from irc.mozilla.org) that result from connecting to an account or joining a channel do not obtrusively open tabs, as you just have to go through them all and close them manually. They especially proliferate on startup.

The question is where to put them instead. Here are some possibilites:

- Put them in hidden conversation tabs 
- Include them as system messages in the conversation tab of the channel being opened
- Hide them completely (since there was no error), but write them to the log
- Write them to a 'console' tab that can be opened from the menu on-demand

Maybe there is an even better way?

Comment 1

[Patrick Cloke [:clokep]]

*** Original post on bio 1013 at 2011-09-02 11:42:24 UTC ***

(In reply to comment #0)
> Unless an error has actually occurred, it would be better if NickServ/ChanServ
> messages (and e.g. the one you get from irc.mozilla.org) that result from
> connecting to an account or joining a channel do not obtrusively open tabs, as
> you just have to go through them all and close them manually. They especially
> proliferate on startup.
Unfortunately we can't really know if an "error" occurs without parsing the content of the messages.

> The question is where to put them instead. Here are some possibilites:
> 
> - Put them in hidden conversation tabs 
While this would help the immediate problem, it would not really be a solution, just glossing over the issue (and would cause more problems for people who have an account, but manually identify every time they log in).

> - Include them as system messages in the conversation tab of the channel being
> opened
NickServ does not belong to a specific conversation though.

> - Hide them completely (since there was no error), but write them to the log
Occasionally you need to respond to what the NickServ/ChanServ says to you (so hiding them completely could cause a user to miss important information), if we were to choose to only show some of them...that's bug 954155 (bio 720).

> - Write them to a 'console' tab that can be opened from the menu on-demand
This has similar issues to above, as you do occasionally need to reply to them, but it's possible something could be worked in this way.

> Maybe there is an even better way?
Not that I could think of. :( We do have an extension to kill them so they never show up though: https://addons.instantbird.org/en-US/instantbird/addon/209 it hasn't been updated for 1.0, but it probably still works.

Comment 2

[Patrick Cloke [:clokep]]

*** Original post on bio 1013 at 2012-06-01 21:37:19 UTC ***

(In reply to comment #0)
> Unless an error has actually occurred, it would be better if NickServ/ChanServ
> messages (and e.g. the one you get from irc.mozilla.org) that result from
> connecting to an account or joining a channel do not obtrusively open tabs, as
> you just have to go through them all and close them manually. They especially
> proliferate on startup.
> 
> The question is where to put them instead. Here are some possibilites:
> 
> - Put them in hidden conversation tabs 
> - Include them as system messages in the conversation tab of the channel being
> opened
This is bug 954905 (bio 1472) (at least the case that I know of).

Comment 3

[aleth [:aleth]]

*** Original post on bio 1013 at 2012-06-29 22:48:03 UTC ***

I think the remainder of this, post-bug 954905 (bio 1472), is bug 954910 (bio 1477), but authentification wasn't even mentioned in the original bug, so resolving this.