prosody-hg: plugins/muc/register.lib.lua history

MUC: Add basic "GC3" participant (affiliation) list fetch

Thu, 26 Jun 2025 15:17:57 +0100

MUC: Add basic "GC3" participant (affiliation) list fetch

RSM version currently held back until a planned restructuring of how we
store affiliations in MUC. This is because RSM needs a stable ordered list,
which we don't currently have.

MUC: Don't allow self-registration into members-only MUCs when unaffiliated registration enabled

Thu, 26 Jun 2025 15:13:29 +0100

MUC: Don't allow self-registration into members-only MUCs when unaffiliated registration enabled

MUC: Fix nickname registration form error handling (fixes #1930)

Mon, 05 May 2025 16:32:45 +0200

MUC: Fix nickname registration form error handling (fixes #1930)

`dataform:data()` always returns the first table of collected values,
even if there are errors, so checking for its absence did not detect
when a required field (the only field, nickname) was missing.

muc.register: Clarify what's going on when enforcing nicknames

Fri, 03 Nov 2023 21:13:34 +0100

muc.register: Clarify what's going on when enforcing nicknames

Does this make it clearer what is going on?

plugins: Prefix module imports with prosody namespace

Fri, 24 Mar 2023 13:15:28 +0100

plugins: Prefix module imports with prosody namespace

MUC: Remove <{muc}x> tags in some errors

Wed, 08 Dec 2021 21:55:25 +0100

MUC: Remove <{muc}x> tags in some errors

Including the payload of the stanza that caused the error is optional
and we're generally not doing it anywhere else.

MUC: Fix error origin JID in wrong argument position

Wed, 08 Dec 2021 21:06:16 +0100

MUC: Fix error origin JID in wrong argument position

Mistake introduced in cbe524ed1a6a. Removing because this is a query to
the bare JID where the error origin matches the resulting stanza 'from'.

MUC: Add option to include form in registration query

Mon, 15 Nov 2021 16:11:03 +0000

MUC: Add option to include form in registration query

This was originally not done based on my interpretation of XEP-0045. Today's
reading, however, revealed that it actually says the result

> SHOULD contain **at least** a element

(emphasis mine)

I take this to mean that including a form **is** allowed (and I think this is
sensible). Tigase already includes the form I believe.

I've gated the new behaviour behind a (default off) option, because it hasn't
been tested for compatibility with clients. My primary desire for it is in
Snikket, where the clients will be tested to ensure compatibility with this.

I don't anticipate that (m)any clients would break, so maybe after 0.12 we can
experiment with enabling it by default and eventually remove the option.

MUC: Allow modules to add to the room registration form, and handle the result

Fri, 15 Jan 2021 18:42:45 +0000

MUC: Allow modules to add to the room registration form, and handle the result

MUC: Enforce strict resourceprep when registering room nicknames

Sat, 02 May 2020 20:12:41 +0200

MUC: Enforce strict resourceprep when registering room nicknames

If nickname enforcement is enabled this would otherwise let you bypass
the join check in muc.lib by registering an invalid nickname and then
joining with any nickname, letting register.lib change it to the invalid
registered nick.

MUC: Indicate origin of registration related errors

Mon, 25 Nov 2019 23:51:41 +0100

MUC: Indicate origin of registration related errors

MUC: Make nickname field in registration form required

Sat, 02 Nov 2019 14:22:06 +0100

MUC: Make nickname field in registration form required

Prevents traceback from resourceprep(nil)

muc#register_roomnick is also required in XEP-0045

Merge 0.11->trunk

Sun, 20 Oct 2019 16:37:04 +0200

Merge 0.11->trunk

MUC: Validate registration dataform more carefully

Sun, 20 Oct 2019 14:54:57 +0200

MUC: Validate registration dataform more carefully

MUC: Don't advertise registration feature on host JID (fixes #1451)

Sun, 20 Oct 2019 01:20:11 +0200

MUC: Don't advertise registration feature on host JID (fixes #1451)

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: Simplify nickname refresh loop

Sun, 25 Aug 2019 21:31:04 +0200

MUC: Simplify nickname refresh loop

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 affiliation (thanks jc)

Thu, 13 Sep 2018 14:46:24 +0100

MUC: If a user with an existing affiliation registers, preserve that affiliation (thanks jc)

MUC: Move comment for clarity

Tue, 04 Sep 2018 11:57:41 +0100

MUC: Move comment for clarity

MUC: Add support for registering with a MUC, including reserving a nickname as per XEP-0045

Mon, 03 Sep 2018 12:26:25 +0100

MUC: Add support for registering with a MUC, including reserving a nickname as per XEP-0045