mod_register currently handles three separate things:
- registration (creation of new accounts)
- password change
- deletion of accounts
The current way of having mod_register enabled but allow_registration = false can be a bit confusing. Separating these three different tasks into two or three modules so that enabling or disabling mod_register really does enable or disable registration might make more sense.
Zash
on
Separating the rate limiting and IP white/blacklists into out would also make sense. Especially if this makes it apply to other kinds of registration modules, eg mod_register_web
mod_register currently handles three separate things: - registration (creation of new accounts) - password change - deletion of accounts The current way of having mod_register enabled but allow_registration = false can be a bit confusing. Separating these three different tasks into two or three modules so that enabling or disabling mod_register really does enable or disable registration might make more sense.
Separating the rate limiting and IP white/blacklists into out would also make sense. Especially if this makes it apply to other kinds of registration modules, eg mod_register_web
ChangesSplit into separate modules in - https://hg.prosody.im/trunk/rev/f591855f060d - https://hg.prosody.im/trunk/rev/0e02c6de5c02
Changes