Summary: |
reconsider mapping of chat state 'gone' |
Product: |
Telepathy
|
Reporter: |
Simon McVittie <smcv> |
Component: |
gabble | Assignee: |
Telepathy bugs list <telepathy-bugs> |
Status: |
RESOLVED
MOVED
|
QA Contact: |
Telepathy bugs list <telepathy-bugs> |
Severity: |
minor
|
|
|
Priority: |
low
|
|
|
Version: |
git master | |
|
Hardware: |
Other | |
|
OS: |
All | |
|
Whiteboard: |
|
i915 platform:
|
|
i915 features:
|
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
We currently send chat state 'gone' when the Telepathy channel is closed, and Empathy closes Text channels when their window is closed. telepathy-spec currently says: # It may not be explicitly sent # It should be automatically sent when the channel is closed The XEP says: > <gone/> > Definition: User has effectively ended their participation in the chat session. > Suggested trigger: User has not interacted with the chat session interface, system, or device for a relatively long period of time (e.g., 10 minutes). which isn't very helpful either. One possible resolution is: * Remove the two quoted bullet points from the spec * Make Gabble not send <gone/> on Close() * If UIs want to send the 'gone' state, they can treat it like any other state