| Summary: |
document why Text clients shouldn't wait for first message |
| Product: |
Telepathy
|
Reporter: |
Simon McVittie <smcv> |
| Component: |
tp-spec | Assignee: |
Telepathy bugs list <telepathy-bugs> |
| Status: |
RESOLVED
MOVED
|
QA Contact: |
Telepathy bugs list <telepathy-bugs> |
| Severity: |
enhancement
|
|
|
| Priority: |
lowest
|
|
|
| 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.
Rescuing this from doc/dispatch.txt before I delete it: Benvolio connects to an irssi-proxy, bip or other IRC bouncer running on some colo box somewhere. The proxy informs his client that he is already in #telepathy and #farsight. ... Problems: * Empathy's filter (notification icon) considers these channels to be incoming and waits for the first received message before blinking the status icon, which means Benvolio thinks his proxy instance has lost its connection to those channels [I think this has been fixed since -smcv] Issues to bear in mind: * These Text channels are neither incoming nor outgoing - they are in a third state, "automatically created". I don't think it's very useful to distinguish between this and incoming, though. Proposed implementation: * The channels have Requested=FALSE, just like incoming channels * Clients should not wait for the first message in an incoming channel - this would break chatroom invitations in any case * If a connection manager creates channels before a message arrives, clients should assume it has a valid reason to do so? ("`psychic mode`_") .. _psychic mode: http://meanwhile.sourceforge.net/faq/#psychic