Mercurial > prosody-modules
view mod_incidents_handling/README.markdown @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Mon, 22 Mar 2021 15:55:02 +0000 |
parents | 8de50be756e5 |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Incidents Handling plugin ... Introduction ============ This module implements [XEP-268](http://xmpp.org/extensions/xep-0268.html). Details ======= It will let you manage reports, inquiries, requests and responses through an Adhoc interface. The following new adhoc admin commands will be available: - List Incidents -- List all available incidents and let's you reply requests. - Send Incident Inquiry -- Inquiry a remote server about an incident. - Send Incident Report -- Send an incident report to a remote server. - Send Incident Request -- Send an incident request to a remote server. Each Adhoc form provides syntax instructions through `<desc/>` elements (they may currently be stripped by Prosody), although it's encouraged to read the [IODEF specifications](https://tools.ietf.org/html/rfc5070). Usage ===== Copy the module folder into your prosody modules directory. Place the module between your enabled modules either into the global or a vhost section. Optional configuration directives: ``` {.lua} incidents_expire_time = 86400 -- Expiral of "closed" incidents in seconds. ``` Info ==== - to be 0.9, works.