Software /
code /
prosody-modules
File
mod_muc_moderation/README.markdown @ 5271:3a1df3adad0c
mod_http_oauth2: Allow user to decide which requested scopes to grant
These should at the very least be shown to the user, so they can decide
whether to grant them.
Considered whether to filter the requested scopes down to actually
understood scopes that would be granted, but decided that this was a bit
complex for a first step, since role role selection and other kinds of
scopes are mixed into the same field here.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 23 Mar 2023 16:28:08 +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)