Mercurial > prosody-modules
view mod_mam_archive/README.markdown @ 4651:8231774f5bfd
mod_cloud_notify_encrypted: Ensure body substring remains valid UTF-8
The `body:sub()` call risks splitting the string in the middle of a
multi-byte UTF-8 sequence. This should have been caught by util.stanza
validation, but that would have caused some havoc, at the very least causing
the notification to not be sent.
There have been no reports of this happening. Likely because this module
isn't widely deployed among users with languages that use many longer UTF-8
sequences.
The util.encodings.utf8.valid() function is O(n) where only the last
sequence really needs to be checked, but it's in C and expected to be fast.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 22 Aug 2021 13:22:59 +0200 |
| 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 ------------ ------------