Mercurial > prosody-modules
view mod_muc_moderation/README.markdown @ 5461:06640647d193
mod_http_oauth2: Fix use of arbitrary ports in loopback redirect URIs
Per draft-ietf-oauth-v2-1-08#section-8.4.2
> The authorization server MUST allow any port to be specified at the
> time of the request for loopback IP redirect URIs, to accommodate
> clients that obtain an available ephemeral port from the operating
> system at the time of the request.
Uncertain if it should normalize the host part, but it also seems
harmless to treat IPv6 and IPv4 the same here.
One thing is that "localhost" is NOT RECOMMENDED because it can
sometimes be pointed to non-loopback interfaces via DNS or hosts file.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 17 May 2023 13:51:30 +0200 |
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)