-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "unavailable" presence state should surely actually be "away" (SPEC-15) #40
Comments
I picked "unavailable" as the state name because in practice the real condition is carried in the string field. The string could say "busy" or "away" or "idle" or whatever. The semantics of the application ought arguably to be the same in all situations. "unavailable" in some way declares that the would-be recipient of the message is unlikely to reply any time soon. "away" would suggest they aren't even going to read it, whereas "busy" might mean "I am at my desk but doing something super-imporant so please don't distract me". ((Also shouldn't this be a SPEC bug?)) -- @leonerd |
bit late now -- @richvdh |
Will be good to implement 2 presence states of users:
This is very useful to see idle info, especially in company messengers: I must know is user near the computer/phone now, or away many hours. At now if user installs Matrix Android client, I always see them as online, even if he turn off company computer and goes to sleep at home. But If away presence info isn't implemented by privacy reasons, let's make this optional "Don't send idle events", like "Don't send typing notifications". |
We currently set a user as "unavailable" if they've been idle for 5 minutes or whatever in the webclient.
In practice, surely "unavailable" should mean "i am busy; go away". Whereas "idle" or "away" should mean "i don't seem to be using Matrix currently".
(Imported from https://matrix.org/jira/browse/SPEC-15)
(Reported by @ara4n)
The text was updated successfully, but these errors were encountered: