Ticket #3593 (closed enhancement: fixed)

Opened 3 years ago

Last modified 3 weeks ago

Message Archiving (XEP-0136)

Reported by: Thomas Owned by: asterix
Priority: normal Milestone: 0.15
Component: history Version:
Severity: normal Keywords:
Cc: michal@…, mcepl@…, phearnot, s.kalyanasundaram@…, silkensedai@…, michael@…, phoenix@…, michael@…, ogi@…, felix@… Blocked By:
OS: All Blocking: 1528

Description

some server support XEP-136 it's a solution like Gtalk to find old messages. I think it's a good idea that Gajim support it.

Attachments

Change History

Changed 3 years ago by misc

For information, I think ejabbrd support it, and I think openfire does too ( not sure for the non commercial version however ).

Changed 3 years ago by Jim++

See also #1528

Changed 3 years ago by mcepl

  • status changed from new to closed
  • cc mcepl@… added
  • resolution set to duplicate

This is reaelly duplicate of 1528.

Changed 3 years ago by mcepl

  • status changed from closed to reopened
  • resolution duplicate deleted

Changed 3 years ago by mcepl

Silly me, it is not duplicate (the other bug is about switching off the recording). OK, so couple of notes here:

Concerning server-side support:

* there is a module for ejabberd ( http://www.ejabberd.im/mod_archive which) has been (apparently -- according to  http://blog.bepointbe.be/index.php/2007/10/09/22-server-archive-online-reader) upgraded to the latest spec.

* there is also a third-party open source plugin for openfire --  http://www.igniterealtime.org/community/docs/DOC-1094

Changed 3 years ago by anonymous

#1282 is duplicate of this

Changed 3 years ago by nijel

  • cc michal@… added

Changed 3 years ago by phearnot

  • cc phearnot added
  • type changed from defect to enhancement

Changed 22 months ago by mcepl

  • component changed from None to history

Changed 22 months ago by mcepl

Actually, the best what I would like to see is storing logs into sotre, which could be sqlite (default), or anything else for which plugin is written (so that even reporter of the unfortunate #1604 could be satisfied if he writes a plugin for the plain text log files), and here it would be stored in the server using XEP-0136 protocol.

Changed 22 months ago by steve-e

Yes, strategy pattern is the way to go here. First step would be to define a sane API.

Any volunteers? :-)

Changed 22 months ago by kalyan

  • cc s.kalyanasundaram@… added

Changed 21 months ago by mildred

  • cc silkensedai@… added

Changed 20 months ago by michael@…

  • cc michael@… added

Changed 19 months ago by phoenix@…

  • cc phoenix@… added

Changed 19 months ago by anonymous

As far as i understand this enhancement is not even on a roadmap?

Changed 19 months ago by anonymous

I think comment 11 is what matters here. So, no, it isn't.

Changed 18 months ago by michael@…

  • cc michael@… added

Changed 15 months ago by mcepl

Changed 15 months ago by asterix

it is of course!

Changed 14 months ago by asterix

  • blocking 1528 added

Changed 12 months ago by http://ogi.myopenid.com/

  • cc ogi@… added

Changed 11 months ago by felix@…

  • cc felix@… added

Changed 3 weeks ago by asterix

  • status changed from reopened to closed
  • resolution set to fixed
  • milestone set to 0.15

message archiving branch has been merged in [71350c946dc3]

Add/Change #3593 (Message Archiving (XEP-0136))

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Next status will be 'needinfo'
 
Note: See TracTickets for help on using tickets.