Software /
code /
prosody-modules
File
mod_invites_register/README.markdown @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parent | 5141:027fb71ad509 |
child | 5482:2f7fff6c8c73 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: 'Allow account registration using invite tokens' ... Introduction ============ This module is part of the suite of modules that implement invite-based account registration for Prosody. The other modules are: - [mod_invites] - [mod_invites_adhoc] - [mod_invites_page] - [mod_invites_register_web] - [mod_invites_api] - [mod_register_apps] For details and a full overview, start with the [mod_invites] documentation. Details ======= This module allows clients to register an account using an invite ('preauth') token generated by mod_invites. It implements the protocol described at [docs.modernxmpp.org/client/invites](https://docs.modernxmpp.org/client/invites) and [XEP-0401 version 0.3.0](https://xmpp.org/extensions/attic/xep-0401-0.3.0.html). **Note to developers:** the XEP-0401 protocol is expected to change in the future, though Prosody will attempt to maintain backwards compatibility with the 0.3.0 protocol for as long as necessary. This module is also responsible for implementing the optional server-side part of [XEP-0379: Pre-Authenticated Roster Subscriptions](https://xmpp.org/extensions/xep-0379.html). **Note to admins:** Loading this module will disable registration for users without an invite token by default. Control this behaviour # Configuration | Name | Description | Default | |--------------------------|----------------------------------------------------------|---------| | registration_invite_only | Require an invitation token for all account registration | `true` | ## Example: Invite-only registration This setup enables registration **only** for users that have a valid invite token. ``` {.lua} allow_registration = true registration_invite_only = true ``` ## Example: Open registration This setup allows completely **open registration**, even without an invite token. ``` {.lua} allow_registration = true registration_invite_only = false ```