[Pidgin] #13507: Status "Busy" with custom message not shown on Yahoo
Pidgin
trac at pidgin.im
Thu Jun 9 12:00:24 EDT 2011
#13507: Status "Busy" with custom message not shown on Yahoo
--------------------+-------------------------------------------------------
Reporter: ciuly | Owner: sulabh.dev
Type: defect | Status: new
Milestone: | Component: Yahoo!/Yahoo! JAPAN
Version: 2.7.11 | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment(by ciuly):
I find it hard to believe that "Yahoo has no distinction between "Busy"
and "Away"".
As I see it, yahoo can be "available" or "busy", and in both cases it can
be "idle" (away). So the "available" and "busy" are statuses and the
"idle" is a state.
You can be "available" AND "idle" and you can be "Busy" AND "idle".
I do not know how the internals of yahoo are implemented, but I do know
what I can set in the client and that it reports back just fine to say the
web client, and back.
Now, the problem with prpl is that it doesn't consider the "idle"/"away"
as a state, but as a separate status. and that is the actual problem.
you have (prpl - yahoo)
available - available
away - available and idle
do not disturb - busy
and the list ends here. prpl needs a status that says: "do not disturb"
and "away" in the same time.
The fact that I am available or busy are 2 things, the fact that I am or
not at the computer (as such away/idle) applies to both statuses.
The otehr weird thing with prpl/yahoo/whatever is that you can set
yourself as being "away" but still be active on your computer. which kind
of makes that status a bit incorrect, doesn't it? You cannot set yourself
as being away (from the computer) but still being there. It's stupid.
The correct way of fixing this is to implement "away" as being a state,
not settable by the user, but by the client itself (configurable time). If
it's easier to implement by creating another status that say "do not
disturb and away" having the away icon with the not disturb red whatever
in center, that's probably fine by any user. People don't really care how
it's implemented as long as it does what it is supposed to and does it
correctly.
--
Ticket URL: <http://developer.pidgin.im/ticket/13507#comment:6>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list