After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633255 - support chat session sync
support chat session sync
Status: RESOLVED DUPLICATE of bug 594062
Product: empathy
Classification: Core
Component: Chat
unspecified
Other All
: Normal enhancement
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-10-27 10:18 UTC by Jakub Steiner
Modified: 2010-10-27 14:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jakub Steiner 2010-10-27 10:18:22 UTC
Currently my android phone IM client feels superior to my desktop client in that it pulls conversations I had with a person on other clients and progressively populates the conversation window as soon as I open it. That way I don't lose bits of the conversation I might have had on my desktop or a notebook. I would love my desktop client to do the same.

Not sure if google has some extensions to the jabber protocol, but it would be neat to have support for this even if for Gtalk only.
Comment 1 Guillaume Desmottes 2010-10-27 10:28:37 UTC
I don't know how the the Android client does that. Maybe by storing logs on the server and fetching them (which is bug #594062).
If you have a chat using Empathy, is it then displayed in Android?
Comment 2 Jakub Steiner 2010-10-27 10:42:46 UTC
Google does log all the conversations as they are searchable from gmail so it may be very specific to gtalk. Conversations done in empathy do sync back up to my phone, yes.
Comment 3 Guillaume Desmottes 2010-10-27 14:52:36 UTC
Ok, so it's probably using google's server logging. Do you know if other clients are able to fetch those logs? I'm wondering if you can get using pure XMPP.

I'm closing this bug as a dup of bug #594062 as that's basically the same request.

*** This bug has been marked as a duplicate of bug 594062 ***