Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#13546 closed defect (invalid)

IRC uses wrong context for part messages

Reported by: foxmajik Owned by: elb
Milestone: Component: IRC
Version: 2.7.11 Keywords: irc
Cc:

Description

When someone leaves a channel Pidgin says:

[nick] left the room (quit: [quit message]).

It should say:

[nick] has quit (quit message).

Saying that someone has left the room when in fact they quit is like saying someone has stopped playing cards when in fact they have died.

Of course they have stopped playing cards, they're dead.

It's unnecessary to say that they have left the room because they have quit, and thus inherently they have left the room.

On a more practical note: If the message says that they have left when in fact they have quit, it is difficult to determine systematically if the user has left the channel or quit.

Change History (2)

comment:1 Changed 8 years ago by elb

  • Resolution set to invalid
  • Status changed from new to closed

It's not at all like that. They left the room because they quit. For most users, in most cases, the important thing is that someone left the room -- why they left the room is secondary.

This is certainly a matter of preference, not not something which is right or wrong. The current implementation fits the Pidgin/libpurple "feel" better, of presenting the most-likely-to-be-important information as the primary information, with ancillary information included where it provides value.

Note that (quit: ) bit in the message. You can systematically determine that a buddy left via quit by looking for that. This is functionally identical to saying 'nick has quit (quit message)'. If the user has left the channel for some other reason, the quit: will not be displayed. It is the case that someone parting with /part quit: whatever will show the same as quit... I would entertain a good suggestion for disambiguating these situations without fundamentally changing the way the message is presented. (For example, freenode uses different quoting for different message origins.)

comment:2 Changed 8 years ago by foxmajik

I agree with your assessment.

It probably fits the libpurple feel better as it is.

Thanks for answering.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!