Mercurial > prosody-modules
view mod_mam_archive/README.markdown @ 5907:d194d1012fd3
Updating dox for mod_rest. Ideas expressed / clarified:
1) Making clear that mod_rest isn't to be installed under VirtualHosts AND as a component.
2) Understanding some of the implications of this choice:
A) Changes to user authentication
B) How it affects subdomains
3) More consistent use of domain names for clarity.
4) Using different heading sizes to show scope of section.
Essentially, I added all the tidbits I had to clarify in getting this to work in my
own example.
author | Ben Smith <bens@effortlessis.com> |
---|---|
date | Mon, 13 May 2024 13:25:13 -0700 |
parents | 758a9a723597 |
children |
line wrap: on
line source
--- 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 ------------ ------------