Summary: | Support closing multi-user chat channels without leaving the room | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Will Thompson <will> |
Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | freedesktop-bugs, mikhail.zabaluev, pedrogfrancisco |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Will Thompson
2009-10-19 04:08:30 UTC
Another case where it is useful, and already implemented, are Skype chats. How about an interface, providing a (requestable) property like "LeaveWhenClosed" and method Leave? In Maemo, we have the latter for Skype-specific chat add-ons interface. > How about an interface, providing a (requestable) property like > "LeaveWhenClosed" That means the channel requester has to know whether the handler supports this new method. I wonder whether we could use <http://telepathy.freedesktop.org/spec/Client_Handler.html#org.freedesktop.Telepathy.Client.Handler.Capabilities> for this? Technically it's imperfect, because if you have two handlers installed—one with and one without this feature—the CM can't tell them apart. But it might be good enough. Similar bug in Empathy: https://bugzilla.gnome.org/show_bug.cgi?id=599184 And downstream Ubuntu: https://bugs.launchpad.net/libtelepathy/+bug/732688 I've implemented the respawning-Close() behaviour for chat rooms in Idle (bug 24273). I feel like time spent making it opt-in could be better spent elsewhere, so I haven't done that. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/39. |
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.