Bug 338904 - Chat log does not preserve jabber resources
Summary: Chat log does not preserve jabber resources
Status: RESOLVED INTENTIONAL
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: log-viewer (show other bugs)
Version: 0.8.1
Platform: Debian unstable Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-08 11:31 UTC by Josef Kufner
Modified: 2014-09-11 12:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot (12.86 KB, image/png)
2014-09-08 11:32 UTC, Josef Kufner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josef Kufner 2014-09-08 11:31:42 UTC
When chatting with myself, log messages are groupped like only one person is sending messages from one place, but he sends messages to another self.

Reproducible: Always

Steps to Reproduce:
1. Open jabber chat to yourself from another jabber client using different resource.
2. Send few messages
3. Open log viewer

Actual Results:  
One text bubble, see screenshot.

Expected Results:  
Multiple text bubbles, like in chat window.
Comment 1 Josef Kufner 2014-09-08 11:32:16 UTC
Created attachment 88611 [details]
Screenshot
Comment 2 David Edmundson 2014-09-08 11:45:50 UTC
Why are you chatting with yourself?
Comment 3 Josef Kufner 2014-09-08 12:17:27 UTC
Why not? :)

It is useful for users with multiple personality disorder and those who send some links, notes or other stuff between multiple devices.

Also when remote user changes his resource, for example uses different device, it should be visible in chat. At least by rendering a new bubble, so the new JID can be rendered.
Comment 4 David Edmundson 2014-09-08 15:29:19 UTC
The log doesn't store this, and the jabber backend doesn't supply resource information.
I'm not going to implement it for such an edge case.
Comment 5 David Edmundson 2014-09-08 15:30:12 UTC
Forgot to say, 
Thanks for submitting a report, hopefully you can understand our resources are limited and we don't want to make code more complex for few users.
Comment 6 Josef Kufner 2014-09-08 17:43:17 UTC
Ok, it sounds reasonable. However, I don't see much complexity in storing backend-specific data.

Does it mean that Telepathy cannot properly handle Jabber? For example reply to correct resource, when original message is from resource of lower priority. Or user cannot choose where to send the message, when he knows where recipient physicaly is and his both clients are online.
Comment 7 Martin Klapetek 2014-09-11 12:54:13 UTC
> Does it mean that Telepathy cannot properly handle Jabber? 

Yes it can. But it does not necessarily expose that information to the clients (which would be KDE Telepathy).

> Or user cannot choose where to send the message, when he knows where recipient physicaly is and his both clients are online.

Nope, we don't provide any user-visible way to do that. We believe that if users need to do such things, they'd be better off with some more advanced Jabber client. Sorry.