view mod_muc_moderation/README.markdown @ 5185:09d6bbd6c8a4

mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow It's optional and the one stored in the client registration should really be used instead. RFC 6749 says an URI provided as parameter MUST be validated against the stored one but does not say how. Given that the client needs their secret to proceed, it seems fine to leave this for later.
author Kim Alvefur <zash@zash.se>
date Thu, 02 Mar 2023 22:00:42 +0100
parents be859bfdd44e
children bb083e9f78dd
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

-   Basic functionality with Prosody 0.11.x and later
-   Full functionality with Prosody 0.12.x and `internal` or `sql`
    storage^[Replacing moderated messages with tombstones requires new storage API methods.]

## Clients

-   [Converse.js](https://conversejs.org/)
-   [Gajim](https://dev.gajim.org/gajim/gajim/-/issues/10107)
-   [clix](https://code.zash.se/clix/rev/6c1953fbe0fa)

### Feature requests

-   [Conv](https://github.com/iNPUTmice/Conversations/issues/3722)[ersa](https://github.com/iNPUTmice/Conversations/issues/3920)[tions](https://github.com/iNPUTmice/Conversations/issues/4227)
-   [Dino](https://github.com/dino/dino/issues/1133)
-   [Poezio](https://lab.louiz.org/poezio/poezio/-/issues/3543)
-   [Profanity](https://github.com/profanity-im/profanity/issues/1336)