Mercurial > prosody-modules

view mod_muc_reserve_nick_pattern/README.markdown @ 5264:d3ebaef1ea7a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_oauth2: Correctly verify OAuth client credentials on revocation Makes no sense to validate against username and password here, or using a token to revoke another token, or itself? In fact, upon further discussion, why do you need credentials to revoke a token? If you are not supposed to have the token, revoking it seems the most responsible thing to do with it, so it should be allowed, while if you are supposed to have it, you should be allowed to revoke it.
author Kim Alvefur <zash@zash.se>
date Tue, 21 Mar 2023 21:57:18 +0100
parents dc6a10629670
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'Require MUC occupant nicknames to no match some patterns'
---

Introduction
============

This checks the nickname of a joining user against a configurable list of
[Lua patterns](https://www.lua.org/manual/5.2/manual.html#6.4.1), and prevents
them from joining if it matches any of them.

Configuration
=============

There is a single configuration option, `muc_reserve_nick_patterns` and the
default is `{}` - i.e. allow everything.

Compatibility
=============

Requires Prosody 0.11 or higher.