File

mod_muc_moderation/README.markdown @ 4065:92152437ecfe

mod_muc_markers: replace configurable multi-marker tracking with better system Now tracks a single marker, but automatically applies rules from the XEP about "higher" markers implying "lower" markers - i.e. "displayed" implies "received". Still, just a single marker is tracked and synthesized at all times (the one configured with muc_marker_name).
author Matthew Wild <mwild1@gmail.com>
date Tue, 07 Jul 2020 17:08:08 +0100
parent 3897:3a96070f4a14
child 4752: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)