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

At 9:42 AM -0700 3/6/02, Colter Reed wrote:
>  > 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"...
>
>Yes, the Yahoo protocol allows you to specify an arbitrary string to show up
>next to your name.
>
>What I think Eric meant is that when one is available, the official clients
>don't clutter your screen by plastering the string "Available" after one's
>name, as it does "Busy" when one is busy.  The available state is indicated
>by a lack of other states.  This does work in Fire.

Ah, ok, so I guess my question instead worded as:

"Is there a way to add 'Status' to the 'Type' pulldown, which would 
be 'functionally equivalent to Available' (e.g., don't autorespond 
with this message when the client receives a new message), but which 
would be used for status-messages on services which allow... well, 
arbitrary status-messages, such as Y!Messenger."

:-)

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