{#}  Replies are directed back to [EMAIL PROTECTED]
{#}  To reply to the author, write to "Derek J. Balling" <[EMAIL PROTECTED]>

At 8:07 AM -0600 3/6/02, Eric Peyton wrote:
>{#}  Replies are directed back to [EMAIL PROTECTED]
>{#}  To reply to the author, write to Eric Peyton <[EMAIL PROTECTED]>
>
>
>On Tuesday, March 5, 2002, at 03:24  PM, Derek J. Balling wrote:
>
>>{#}  Replies are directed back to [EMAIL PROTECTED]
>>{#}  To reply to the author, write to "Derek J. Balling" <[EMAIL PROTECTED]>
>>
>>>- You can specify whether an away message is Away, Busy, Idle or 
>>>Available (cr)
>>
>>This still does not work for Yahoo!.  If I set a message as 
>>"Available" and select it, Yahoo users still do not see it as my 
>>status message. :-/
>>
>
>That's because of the yahoo protocol.  Yahoo doesn't have an 
>"Available" status as far as I am aware.

If I use the "official" client (Which, for now, uses the same 
protocol as libyahoo), I can set a status message which has nothing 
to do with "away" or "idle" status. There's even a plugin for Winamp 
to set the Yahoo!Messenger status to be the "current playing track", 
without affecting "Away"-ness or anything like that... :)

So the protocol DOES support that... In fact, I think the whole 
concept of setting up messages as a "type" of message 
(away/idle/etc.) came because I was noting this same "missing 
feature" in Yahoo a while back. (the archives don't go far enough 
back for me to find where we chatted about that originally, leading 
to a discussion about the merits of "defining message-types"...

D


-- 
+---------------------+-----------------------------------------+
| [EMAIL PROTECTED]  | "Thou art the ruins of the noblest man  |
|  Derek J. Balling   |  That ever lived in the tide of times.  |
|                     |  Woe to the hand that shed this costly  |
|                     |  blood" - Julius Caesar Act 3, Scene 1  |
+---------------------+-----------------------------------------+

{#} ----------------------------------------------------+[ fire ]+---


Reply via email to