Software /
code /
prosody-modules
File
mod_mam_archive/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +0200 |
parent | 1903:758a9a723597 |
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 ------------ ------------