Shows GONE notifications in IMs

[shreevatsa]

Pidgin shows an annoying "<buddy> has left the conversation" message each time the buddy closes his window, at least on XMPP. This is new in 2.0.1.

I think enabling/disabling showing these (GONE notifications) should be made an option, maybe in the Buddy State Notification plugin.

[seanegan]

We need to team you up with all the MSN users complaining that we removed the "buddy has left the conversation" messages for them. Let you all duke it out and then side with the winning team :)

Adding this to the Buddy State Notification plugin is not an unreasonable idea, although I kinda want to see that plugin killed and brought back to the core.

[elb]

I agree that this notification should be displayed only for chats.

[mrjeffreed]

Just a blip to keep this on the radar.

[shreevatsa]

FWIW, I no longer think this is annoying, and it's quite useful to have this information... I even reported it in the first place only because elb encouraged me to :) [There *are* some people who keep closing windows compulsively, so it would be better as an option, but I can live with it.]

[seanegan]

Perhaps a more important issue is a preference for *sending* these notifications. We could probably get away with overloading the "send typing notifications" preference for that.

[seeboo]

It would be great to have these GONE notifications also for ICQ.

[Zsolti]

Please, please, please, let me turn this feature off. (Not just like this: http://developer.pidgin.im/ticket/2606 ; Besides, I don't know how to apply this patch.) It is a chat-like behaviour that is irrelevant in private conversations. Closing the window --IMHO-- has nothing to do with the fact whether I leave the conv. or not.

[shreevatsa]

Replying to Zsolti:

Actually, closing the window _is_ the same as leaving the conversation (why not?). After adopting and getting used to this model, I (and all my Pidgin-using friends) have come to find this useful, although we have had to change some habits of course. Now I can see why the MSN users want this feature so much...

You can already turn it off by disabling sending of typing notifications, so what's the problem?

[Zsolti]

1. OK, I can disable typing notifications, but that's not what I want to do.

2. I'm usually closing the conv. window even if waiting for the answer. So I don't actually leave the conversation, just don't want the window to stay in the taskbar. Bad habit, I know! And even if I close the window, I don't want other Pidgin users to see this.

After all, this is a good feature if you want it / if it fits your habits. Still, I would like to turn _this_ off. (Not the typing notif. that I especially like with the ghost plugin.)

Thank you very much for the answer though!

Replying to shreevatsa:

Replying to Zsolti: Actually, closing the window _is_ the same as leaving the conversation (why not?). After adopting and getting used to this model, I (and all my Pidgin-using friends) have come to find this useful, although we have had to change some habits of course. Now I can see why the MSN users want this feature so much... You can already turn it off by disabling sending of typing notifications, so what's the problem?

[rlaager]

With the merge of the persistent conversation code, I doubt this is an issue any more.

[nowheredan]

I'm with Zsolti - I wish this was a separate option. I like seeing when my friends are typing, but I don't like seeing when they've closed a window.

[emptyowe]

Any chance to get this reconsidered? I too like the notification of typing, but not the auto-send of "left the conversation". I, like Zsolti, close the window when waiting for a response. Some users/clients get put off seeing the "left the conversation" message, even though I'm just decluttering my taskbar while waiting on them. Seems like this should be configurable on/off and not grouped with typing notification. Even enabling/disabling this through backend config files would be acceptable. Thanks for the great product! -M

[nexus]

Replying to rlaager:

With the merge of the persistent conversation code, I doubt this is an issue any more.

You doubt it is an issue anymore, so you marked it as fixed? I am running 2.2.2 and it is still an issue.

[rlaager]

Replying to nexus:

Replying to rlaager:

With the merge of the persistent conversation code, I doubt this is an issue any more.

You doubt it is an issue anymore, so you marked it as fixed? I am running 2.2.2 and it is still an issue.

The conversation persistence code is in trunk and hasn't been released yet.

[nexus]

Replying to rlaager:

Replying to nexus:

Replying to rlaager:

With the merge of the persistent conversation code, I doubt this is an issue any more.

You doubt it is an issue anymore, so you marked it as fixed? I am running 2.2.2 and it is still an issue.

The conversation persistence code is in trunk and hasn't been released yet.

Ah, ok. So shouldn't the milestone be changed from 2.2.1?

[emptyowe]

I hate to look like a newb (I've been using the software for a while now)... but did this actually make it into 2.3.0? From the change history log, it looked like we'd have an option once in a conversation to make that convo persistent. Am I just not looking in the right place? I do not see that option. Also, is it possible to make ALL convos persist by default? Thanks. (Sorry for putting this in the ticket, but I see nowhere else to post. Is there a forum or something?)

[Zsolti]

They did. (Thank you!)

Preferences > Conversations > 2nd option : "Close IMs immediately..."

Replying to emptyowe:

I hate to look like a newb (I've been using the software for a while now)... but did this actually make it into 2.3.0? From the change history log, it looked like we'd have an option once in a conversation to make that convo persistent. Am I just not looking in the right place? I do not see that option. Also, is it possible to make ALL convos persist by default? Thanks. (Sorry for putting this in the ticket, but I see nowhere else to post. Is there a forum or something?)