mod_cloud_notify: Rename field in event for clarity ('node' is ambiguous here)
...because the push protocol is based on XEP-0060, and the 'node' can mean the
identifier communicated to the push service.
---
labels:
- 'Stage-Alpha'
summary: 'XEP-0136: Message Archiving frontend for mod\_mam'
...
Introduction
============
Implementation of [XEP-0136: Message
Archiving](http://xmpp.org/extensions/xep-0136.html) for
[mod\_mam](mod_mam.html).
Details
=======
See [mod\_mam] for details.
Usage
=====
First configure mod\_mam as specified in it's [wiki][mod\_mam]. Make
sure it uses sql2 storage backend.
Then add "mam\_archive" to your modules\_enabled list:
modules_enabled = {
-- ...
"mam_archive",
-- ...
}
Configuration
=============
Because of the fact that [XEP-0136] defines a 'conversation' concept not
present in [XEP-0313], we have to assume some periods of chat history as
'conversations'.
Conversation interval defaults to one day, to provide for a convenient
usage.
archive_conversation_interval = 86400; -- defined in seconds. One day by default
That is the only reason SQL database is required as well.
Compatibility
=============
------ ---------------
0.10 Works
0.9 Does not work
------ ---------------
------------ ------------
PostgreSQL Tested
MySQL Not tested
SQLite Tested
------------ ------------