Bug 31327 - document why Text clients shouldn't wait for first message
Summary: document why Text clients shouldn't wait for first message
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: git master
Hardware: Other All
: lowest enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-02 09:07 UTC by Simon McVittie
Modified: 2019-12-03 20:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Simon McVittie 2010-11-02 09:07:40 UTC
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
Comment 1 GitLab Migration User 2019-12-03 20:22:51 UTC
-- 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/89.


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.