Mercurial > prosody-modules
view mod_muc_moderation/README.markdown @ 5796:93d6e9026c1b
mod_http_oauth2: Do not enforce PKCE on Device and OOB flows
PKCE does not appear to be used with the Device flow. I have found no
mention of any interaction between those standards. Since no data is
delivered via redirects in these cases, PKCE may not serve any purpose.
This is mostly a problem because we reuse the authorization code to
implement the Device and OOB flows.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 15 Dec 2023 12:10:07 +0100 |
parents | d4b97eaeb235 |
children | 593312fedfe1 |
line wrap: on
line source
--- summary: Let moderators remove spam and abuse messages --- # 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.] - Works with [mod_storage_xmlarchive] ## 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 - [Conversations](https://codeberg.org/iNPUTmice/Conversations/issues/20) - [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)