Adium

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#9051 closed enhancement (fixed)

Jabber presence doesn't reflect 'Busy' State setting as 'Do Not Disturb'

Reported by: islandsvinur Owned by: nobody
Milestone: Adium 1.2.3 Component: Service/XMPP (Jabber)
Version: Severity: normal
Keywords: presence away busy Cc:
Patch Status:

Description

Using the terminology of the Custom Status window.

I have a set of custom away status messages (tv, film, work, etc), some of them are of state Away (tv, film), others of state Busy (work). When I choose Busy, it doesn't actually set the Jabber presence to busy, so I appear away to others instead of busy.

Thus I hear from my friends I have what we colloquially call a "lying client" :)

Change History (10)

comment:1 Changed 13 years ago by islandsvinur

And by busy I mean dnd. But the rfc (http://www.ietf.org/rfc/rfc3921.txt section 2.2.2.1) is a bit unclear about whether busy should be dnd or not:

o dnd -- The entity or resource is busy (dnd = "Do Not Disturb").

comment:2 Changed 13 years ago by Evan Schoenberg

Are you selecting "Busy" or "Do Not Disturb" in the Custom Status window?

comment:3 Changed 13 years ago by islandsvinur

Oh sorry, I just realise I made it ambiguous.

I select Busy in the Custom Status window.

My point is that being Busy is certainly not being Available, yet it is a little bit weaker than really not wanting to be disturbed. XMPP doesn't have a state between availability and dnd-ness, and the RFC says about dnd that it means that the entity is busy, so that Busy should be mapped to dnd, not to available.

I think the source of my confusion lies in #8329 (all status icons are the same for non-available states), once that is fixed, this bugreport will become irrelevant. I selected another theme and can live with it as it is now.

comment:4 Changed 13 years ago by Evan Schoenberg

Summary: Jabber presence doesn't reflect State settingJabber presence doesn't reflect 'Busy' State setting as 'Do Not Disturb'

Busy, which XMPP doesn't support, maps to Away, with the message of your choice (which is what you indicate in the description of this ticket.. not 'available' as you indicate in the comment above). You only see 'Busy' in the list if you have enabled a service which does support it (e.g. MSN). If you don't select a message at all with your 'Busy' status, you'll get a message of "Busy" on XMPP (with a status of Away).

The real question here is: Should 'Busy', a non-XMPP state, be considered 'Do Not Disturb' or 'Away', the two closest XMPP states? I think it is indeed closer to 'Do Not Disturb'.

comment:5 Changed 13 years ago by Jordan

Milestone: Needs feedback from users

I agree that it does seem to be closer to do not disturb, since busy often implies you're there but working on something and would rather people only disturb you for 'emergencies'. I feel that is close to do not disturb; at least closer than away, since away usually means you're not there at all.

Perhaps then the state used by Away for XMPP should be DND? What do others think?

comment:6 Changed 13 years ago by Sjoerd Simons

Most xmpp clients i've used use dnd and busy interchangably.. Essentially Busy has two meanings to people:

  • I am busy, if you send me messages it may take a while before i react
  • I am busy, please don't send me messages unless they're really really important

The second meaning is more the way you'd think about busy in the meaning of dnd. The xmpp RFC is a bit strange in that it seems to assumes busy always has the second meaning.

But what imho is the most important part; In whatever way you interpret busy/dns, it always indicates: User is behind/around the computer.. Which an Away state very much contradicts.

comment:7 Changed 13 years ago by Jordan

Milestone: Needs feedback from usersAdium X 1.2.3

Yeah... I agree with those points. Setting appropriates for adjustment. My last line in my comment should have said, "Perhaps then the state used by Busy for XMPP should be DND" rather than Away.

comment:8 Changed 13 years ago by Evan Schoenberg

Resolution: fixed
Status: newclosed

(In [22678]) Treat Busy as DND for XMPP. Fixes #9051

comment:9 Changed 13 years ago by Evan Schoenberg

(In [22679]) Merged [22678]: Treat Busy as DND for XMPP. Fixes #9051

comment:10 Changed 13 years ago by Robert

Milestone: Adium X 1.2.4Adium X 1.2.3
Note: See TracTickets for help on using tickets.