Bug 90838 - Implement XEP-0313: Message Archive Management (MAM)
Summary: Implement XEP-0313: Message Archive Management (MAM)
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on: 23844
Blocks: 96921
  Show dependency treegraph
 
Reported: 2015-06-04 02:10 UTC by Steven Roose
Modified: 2019-12-03 20:01 UTC (History)
7 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Steven Roose 2015-06-04 02:10:41 UTC
> It is a common desire for a user using XMPP for IM to want to store their messages in a central archive on their server. This feature allows them to record conversations that take place on clients that do not support local history storage, and also to synchronise their conversation history seamlessly between multiple clients.

Implementing new XEP's on Telepathy does improve a lot of clients that depend on it. The developers of those are all dependent on Telepathy changes...
Comment 1 Nick Brown 2015-11-09 17:51:21 UTC
Probably very relate or a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=23844
I'd guess that XEP-0313 support should be implemented in logger component of telepathy.
Comment 2 diane 2016-07-13 20:01:51 UTC
As I understand it the telepathy spec does need to be extended to support retrieving historical messages however once that's available, then gabble will still need support for XEP-0313 to go retrieve those logs
Comment 3 GitLab Migration User 2019-12-03 20:01:15 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-gabble/issues/277.


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.