Summary: | Chat log does not preserve jabber resources | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | Josef Kufner <jk> |
Component: | log-viewer | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | kde, mklapetek |
Priority: | NOR | ||
Version: | 0.8.1 | ||
Target Milestone: | Future | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot |
Description
Josef Kufner
2014-09-08 11:31:42 UTC
Created attachment 88611 [details]
Screenshot
Why are you chatting with yourself? 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. 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. 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. 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. > 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. |