Mercurial > prosody-modules

view mod_muc_moderation/README.markdown @ 4515:2e33eeafe962

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 3a96070f4a14
children 67848bf6b425
line wrap: on
line source

# Introduction

This module implements [XEP-0425: Message Moderation].

# Usage

Moderation is done via a supporting client and requires a `moderator`
role in the channel / group chat.

# Configuration

Example [MUC component][doc:chatrooms] configuration:

``` {.lua}
VirtualHost "channels.example.com" "muc"
modules_enabled = {
    "muc_mam",
    "muc_moderation",
}
```

# Compatibility

-   Should work with Prosody 0.11.x and later.
-   Tested with trunk rev `52c6dfa04dba`.
-   Message tombstones requires a compatible storage module implementing
    a new message replacement API.

## Clients

-   Tested with [Converse.js](https://conversejs.org/)
    [v6.0.1](https://github.com/conversejs/converse.js/releases/tag/v6.0.1)