Mercurial > prosody-modules
view mod_muc_auto_member/README.markdown @ 5626:a44af1b646f5
mod_http_oauth2: Optionally enforce authentication on revocation endpoint
But why do OAuth require this? If a token leaks, why couldn't anyone
revoke it?
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 31 Jul 2023 02:07:58 +0200 |
parents | 243c156074d3 |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: "Automatically register new MUC participants as members" ... # Introduction This module automatically makes anybody who joins a MUC become a registered member. This can be useful for certain use cases. Note: there is no automatic cleanup of members. If you enable this on a server with busy public channels, your member list will perpetually increase in size. Also, there is currently no per-room option for this behaviour. That may be added in the future, along with membership expiry. # Configuration There is currently no configuration for this module. The module should be enabled on your MUC component, i.e. in the modules_enabled option under your Component: ``` {.lua} Component "conference.example.com" "muc" modules_enabled = { "muc_auto_member"; } ``` # Compatibility 0.12 and later.