File

mod_muc_moderation/README.markdown @ 5214:d5492bc861f6

mod_http_oauth2: Remove authorization codes after use RFC 6749 section 4.1.2 says: > The client MUST NOT use the authorization code more than once. Thus we clear it from the cache after use.
author Kim Alvefur <zash@zash.se>
date Mon, 06 Mar 2023 16:53:27 +0100
parent 5127:be859bfdd44e
child 5484: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)