| Summary: | Haze: implement Protocol.Interface.Presences | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
| Component: | haze | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | medium | CC: | smcv, xclaesse |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 13125 | ||
| Bug Blocks: | |||
|
Description
Guillaume Desmottes
2013-09-19 12:32:08 UTC
I think this is actually unimplementable, unless we admit defeat and have Haze store accounts long-term (i.e. break the statelessness of accounts): libpurple won't tell you which statuses are going to be available until you create the PurpleAccount. (In reply to comment #1) > (i.e. break the statelessness of accounts) er, the statelessness of connections/connection managers. Some account UI does not let you create an account until it first succeed at connecting. I think it makes sense, and we could cache such info at that moment. *** Bug 31107 has been marked as a duplicate of this bug. *** -- 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-haze/issues/65. |
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.