| Summary: |
Connection's selfContact object should initially have no features |
| Product: |
Telepathy
|
Reporter: |
Simon McVittie <smcv> |
| Component: |
tp-qt | Assignee: |
Telepathy bugs list <telepathy-bugs> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Telepathy bugs list <telepathy-bugs> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| 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.
15:21 < smcv> andrunko: I don't think the self-contact should have Alias, AvatarToken or SimplePresence by default 15:21 < smcv> andrunko: it should just have the core Contact things (handle and identifier) 15:21 < andrunko> smcv, we don' t have support for contact features on connection for now, and oggis_ prefer to enable all contact features for now 15:22 < andrunko> channel also enable all features for now 15:22 < andrunko> oggis_, ^ 15:22 < smcv> andrunko, oggis_: I strongly disagree. having fewer features auto-enabled is better - moving a feature from "you always get it" to "you have to ask for it" is error-prone, moving the other way is easy 15:23 < smcv> and if you auto-enable alias, avatar token and simple presence, that's several signals that will wake up every tp-qt4 client whether it cares or not 15:24 < smcv> of course, *later*, having a way to say "by the time you announce a contact on this channel, I want its alias" would be great 15:24 < smcv> (more so for channels than for the self-contact, though, I think) 15:24 < andrunko> yes that[ s the intention 15:25 < smcv> I think when the self-contact changes it should be announced asap, even if it doesn't have its alias/misc yet 15:25 < smcv> since being able to answer "which of these people is me?" correctly is quite important