|
|
The problem of away messages....: msg#00172
network.jabber.py-transports
|
Subject: |
The problem of away messages.... |
Hi folk!
A while ago someone brought up that pyaim should be sending it's away
messages via an actual autoresponse message when someone writes. I
implemented that, no problem. I also commented that I was concerned
that clients would "do their own thing" too. Well, I now have a
prime example of that. ;) My wife mentioned the other day that when
she writes me and I have an away message, she gets it back 3 times.
Once is ichat showing the away message as it knows it from status
information. Another is because pyaim responds with an auto-response
away message. A third is because my client (adiumx) sends yet
another autoresponse with the away message in it.
So.. 2 copies of the message I understand a little bit more. I mean
yeah, ok, your client shows the message and it's also send via im.
You can't know what the client on the other end is doing and whether
it's going to bother showing the known status-based away message upon
a new im. But then you also can't know that I'm running adiumx which
will be a good monkey and send it's own copy of the away message. 3
is kinda ridiculous. 2 is annoying. 1 is happy. 0 is bad.
So my question to you all is... is there anything you can think of
to help resolve some of these issues? Looking for brainstorming, so
don't be afraid to post whatever "crazy" or "not crazy" idea you
might have. =)
Daniel
|
|