prosody-modules
db4c66a1d24b
mod_muc_mam_markers/README.markdown
Software / code / prosody-modules
File
mod_muc_mam_markers/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 | 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.
