view mod_muc_mam_markers/README.markdown @ 4942:e7b9bc629ecc

mod_rest: Add special handling to catch MAM results from remote hosts Makes MAM queries to remote hosts works. As the comment says, MAM results from users' local archives or local MUCs are returned via origin.send() which is provided in the event and thus already worked. Results from remote hosts go via normal stanza routing and events, which need this extra handling to catch. This pattern of iq-set, message+, iq-result is generally limited to MAM. Closest similar thing might be MUC join, but to really handle that you would need the webhook callback mechanism.
author Kim Alvefur <zash@zash.se>
date Mon, 16 May 2022 19:47:09 +0200
parents a1fc677d0cc8
children
line wrap: on
line source

---
labels:
- 'Stage-alpha'
summary: Save received chat markers into MUC archives'
...

Introduction
============

Chat markers (XEP-0333) specification states that markers _SHOULD_ be
archived.  This is already happening in one to one conversations in
the personal archives but not in Group Chats.  This module hooks the
_muc-message-is-historic_ event to customize the `mod_muc_mam`
behavior and have the chat markers archived.

Usage
=====

First copy the module to the prosody plugins directory.

Then add "muc\_mam\_markers" to your `modules\_enabled` list in your
MUC component's definition.

No configuration options are available.