+++ This bug was initially created as a clone of Bug #22814 +++ 12:02 < Mithrandir> davyd: the suggestion in http://people.collabora.co.uk/~davyd/telepathy-book/sect.messaging.rich.html on not acking messages until they've been parsed so you get it again when the client reloads is a bit of a double edged sword, since you can then get into a crash scenario you can't get out of 12:03 < wjt> Mithrandir: the channel dispatcher solves that 12:03 < davyd> Mithrandir: yes, except Channel Dispatcher 12:03 < wjt> Mithrandir: it's responsible for blowing away a channel if its handler repeatedly dies 12:03 < Mithrandir> ah 12:03 < davyd> we probably should mention that If we're going to do that, MC should actually implement the documented behaviour :-)
-- 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-mission-control/issues/10.
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.