Version: 0.7.1 (using KDE 3.1.3) Installed from: compiled sources Compiler: gcc version 3.2.2 OS: Linux (i686) release 2.4.22.2-mark-athlon- have a possibility to set the auto responder when automattically set away.
MSN has already this. What protocol are you talking about particulary? others protocol have specific away messages
I just mean the set away globally - otherwise i cant set an autoresponder can i?
There used to be an auto responder. It didn't work exactly as I would have hoped (it would auto respond even though I'd just sent a message to the person, it should be smart enough to know not to respond in that case) but it was better than nothing. In a not-too-lang-ago cvs update it stopped auto responding. I also would like to see it put back in or fixed if it's just broken. I only use an AIM account; I don't know if this is all protocol specific.
A lot of people find auto responders extremely annoying. I would rather see this as some kind of plugin then in kopete core.
I disabled it on purpose because it's unneded. both icq and aim have a different (less annoying) way to get/set away messages. I agree with Jason on making this a plugin because this does not need any special handling on most protocols (well, AIM has a "is away message" flag for IMs but otoh who cares anyway, most AIM-clients display it like a normal message).
I find it EXTREMELY annoying to have that auto-responder to say its stuff every minute or so when i'm talking to a person when in away mode.. It drives the people i'm talking to crazy as well.. Please make it an optional thingy, or a plugin.. With that AutoMessage telling i'm away every few lines, it makes chatting while away an annoying action :p
How come nobody has voted vor this bug/wish? I just installed kopete and must say that it's not really pleasant to use in away mode in msn. The automessages are just sooo bothersome, sorry to say this. And also you have the feeling that you can turn them off in the msn account (connection -> send away messages), but it doesn't change anything.
An auto-responder would be very handy. People often message me when I'm away and get confused when there is no auto-response and think I am ignoring them. Of course, it should be an option that the user can change, since in some circumstances they can be annoying, but the user should have the choice.
I use Trillian on Windows and Kopete's autoresponder would do best to mimic Trillian's. In addition / instead of the "Send autoresponse every x seconds" message, Kopete should only send the autoresponse once while a window stays open. That way I can carry on a chat while marked as away and won't be bugged by the autoresponder.
*** Bug 77005 has been marked as a duplicate of this bug. ***
I would like to add the fact that the last-selected automessage is used when going auto-away, even when you set it to online again. So when I set it to "go play, I'm having lunch...", have lunch, come back from lunch and set it to online again and I were to leave the computer a while later, I'm having lunch again againt my will... Kopete version: 0.9.2 KDE: 3.3.2
That should really be improved. I actually never checked it but I have wondered why there was no auto-away message selection.
If you have time and ideas on how to improve this, we would welcome a patch. Right now, none of the current developers have time to do this.
I have ideas but I cannot program in C++. This is easiest to fix with bug #57297 and allowing people to save their away messages. Then simply adding a box where users can choose an away message and the problem is solved (yea, the "set auto away" code needs to be edited a bit).
I have implemented this feature in the AIM protocol. It it hard coded to send away messages to a contact only once every 2 minutes, but this should be configurable and maybe a little smarter (like not send autoresponses if you're typing to the person) so I'll probably put a little more work into this. Once the pattern is established maybe work can be done to refactor this behavior upwards so more protocols can use it, I'm pretty sure most protocols support this internally, and if not, it can be simulated for the ones that don't support it.
*** Bug 104985 has been marked as a duplicate of this bug. ***
*** Bug 104550 has been marked as a duplicate of this bug. ***