Software /
code /
prosody-modules
File
mod_muc_mam_markers/README.markdown @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parent | 3499:a1fc677d0cc8 |
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.