File

mod_muc_auto_reserve_nicks/README.md @ 5264:d3ebaef1ea7a

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
parent 4772:85d4ab318d66
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'Automatically reserve nicknames of MUC users'
...

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

This module automatically reserves the nickname of a user when they first join
a MUC. That's all.

Details
=======

The module doesn't currently update the registration if the user changes their
nick. That could cause flip-flopping if the user has two clients in regular
use with different nicks configured.

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

Requires Prosody trunk (0.12) for the API introduced in commit
[0e7dedd8b18d](https://hg.prosody.im/trunk/rev/0e7dedd8b18d) and
[e0b58717f0c5](https://hg.prosody.im/trunk/rev/e0b58717f0c5).