Closed
Bug 954602
Opened 11 years ago
Closed 11 years ago
Auto-reply in IRC DMs when user status = away
Categories
(Chat Core :: IRC, defect)
Chat Core
IRC
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: aleth, Unassigned)
Details
*** Original post on bio 1170 at 2011-11-15 23:05:00 UTC ***
When an IRC DM is in progress and the user status is not set to "Available", the chat partner sees messages like "Auto-reply - Away" every time he sends a message. To the IB user, this is invisible. This is rather annoying, especially as (as far as I know) IB does not support auto-reply messages.
Comment 1•11 years ago
|
||
*** Original post on bio 1170 at 2011-11-15 23:11:21 UTC ***
Instantbird notifies the server that you're away (as far as I know), then the server decides what to do with this. Some servers will auto-reply to private messages (this is pretty common on most IM networks).
What part of this is annoying? That you don't see the messages? That you're set to away on the server? I'm not sure what a "auto-reply message" has to do with this.
Reporter | ||
Comment 2•11 years ago
|
||
*** Original post on bio 1170 at 2011-11-15 23:18:35 UTC ***
In a normal conversation, you don't get a message "this user is away" every time you say something just because you are chatting to someone whose status is "unavailable". I posted the bug because I got a complaint about this behaviour from someone I was chatting to, and I had no idea what it was at first since I couldn't see it.
Since this is apparently not due to IB but due to the IRC server (mozilla.org in this case) will set to INVALID.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Comment 3•11 years ago
|
||
*** Original post on bio 1170 at 2011-11-15 23:45:02 UTC ***
So, after investigating a bit more, it seems the server is sending the message every time, but Instantbird is choosing to display it every time. I'm not sure what the proper behavior is in this situation.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 4•11 years ago
|
||
*** Original post on bio 1170 at 2011-11-16 13:32:26 UTC ***
This is definitely one of the most annoying behaviors of the libpurple IRC protocol plugin.
We should show this auto-reply message (sent back by the server after each message we send) only if we have a reason to believe it will be of interest to the user.
Mook proposed on IRC (http://log.bezut.info/instantbird/111115#m687) a behavior that seemed to make sense: "suppress displaying it until either the window is closed/hidden, the away message changes, or it changes (so if the user comes back and goes away again with the same message, show it anyway, if possible)?"
So basically, display the message when it first appears, then remember it, and if the same message is sent again, don't display it. I don't think putting the conversation on hold (which isn't even visible for the prpl plugin) should change anything to the behavior.
We may want to redisplay the message after a few minutes. For example, if I'm talking to foo who is away, I'll see the auto-reply message immediately, then I'm sending a few more messages without seeing the auto-reply again, then if I come back N (5? 20?) minutes later to say something more, I'll see the message again.
Updated•11 years ago
|
Component: General → IRC
Hardware: x86 → All
Reporter | ||
Comment 5•11 years ago
|
||
*** Original post on bio 1170 at 2012-03-01 01:19:15 UTC ***
Update: Current JS-IRC behaviour seems to be "never send an away autoreply", which is much better than before :)
Comment 6•11 years ago
|
||
*** Original post on bio 1170 at 2012-04-03 12:37:54 UTC ***
(In reply to comment #5)
> Update: Current JS-IRC behaviour seems to be "never send an away autoreply",
> which is much better than before :)
So it seems like the original reason this was filed no longer occurs, but now we NEVER show it? That's not good either.
Comment 7•11 years ago
|
||
*** Original post on bio 1170 at 2012-04-03 12:50:19 UTC ***
This is no longer valid as it's a bug in the libpurple IRC protocol. See bug 954792 (bio 1358) about the issues with JS-IRC.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•