Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | MUC: Indicate origin of registration related errors | Kim Alvefur | 2019-11-25 | 1 | -3/+3 |
| | |||||
* | MUC: Make nickname field in registration form required | Kim Alvefur | 2019-11-02 | 1 | -1/+1 |
| | | | | | | Prevents traceback from resourceprep(nil) muc#register_roomnick is also required in XEP-0045 | ||||
* | Merge 0.11->trunk | Kim Alvefur | 2019-10-20 | 1 | -2/+0 |
|\ | |||||
| * | MUC: Don't advertise registration feature on host JID (fixes #1451) | Kim Alvefur | 2019-10-20 | 1 | -2/+0 |
| | | | | | | | | | | | | | | | | | | | | | | There is currently no mention in XEP-0045 of how or where to advertise support for registration. Advertising on the host JID may be confusable with service-wide registration, as implemented in ejabberd. A common and sensible pattern in XMPP is that a feature is advertised on the JID where the service is available. | ||||
* | | MUC: Validate registration dataform more carefully | Kim Alvefur | 2019-10-20 | 1 | -1/+13 |
| | | |||||
* | | MUC: Simplify nickname refresh loop | Kim Alvefur | 2019-08-25 | 1 | -2/+1 |
|/ | | | | Affiliation data is passed as a loop variable so no need to retrieve it | ||||
* | MUC: If a user with an existing affiliation registers, preserve that ↵ | Matthew Wild | 2018-09-13 | 1 | -1/+1 |
| | | | | affiliation (thanks jc) | ||||
* | MUC: Move comment for clarity | Matthew Wild | 2018-09-04 | 1 | -1/+1 |
| | |||||
* | MUC: Add support for registering with a MUC, including reserving a nickname ↵ | Matthew Wild | 2018-09-03 | 1 | -0/+195 |
as per XEP-0045 |