Mercurial > prosody-modules
view mod_muc_moderation/README.markdown @ 4260:c539334dd01a
mod_http_oauth2: Rescope oauth client config into users' storage
This produces client_id of the form owner@host/random and prevents
clients from being deleted by registering an account with the same name
and then deleting the account, as well as having the client
automatically be deleted when the owner account is removed.
On one hand, this leaks the bare JID of the creator to users. On the
other hand, it makes it obvious who made the oauth application.
This module is experimental and only for developers, so this can be
changed if a better method comes up.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sat, 21 Nov 2020 23:55:10 +0100 |
| 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)