Tue, 16 Nov 2021 12:57:23 +0000 MUC: Include old affiliation data in affiliation change event
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 12:57:23 +0000] rev 11916
MUC: Include old affiliation data in affiliation change event
Tue, 16 Nov 2021 12:57:04 +0000 MUC: Add room:set_affiliation_data()
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 12:57:04 +0000] rev 11915
MUC: Add room:set_affiliation_data()
Tue, 16 Nov 2021 12:02:54 +0000 MUC: Set .previous_affiliation = "none" if nil, for consistency with .affiliation
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 12:02:54 +0000] rev 11914
MUC: Set .previous_affiliation = "none" if nil, for consistency with .affiliation It appears nothing currently uses this field in prosody or prosody-modules
Tue, 16 Nov 2021 11:54:32 +0000 MUC: Fix incorrect variable name (thanks luacheck)
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 11:54:32 +0000] rev 11913
MUC: Fix incorrect variable name (thanks luacheck)
Tue, 16 Nov 2021 11:52:36 +0000 MUC: Switch to event.allowed signaling to block event, matching muc-pre-set-role
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 11:52:36 +0000] rev 11912
MUC: Switch to event.allowed signaling to block event, matching muc-pre-set-role ...and fixing the logic bug that broke everything in the previous commit.
Tue, 16 Nov 2021 11:41:08 +0000 MUC: Add 'muc-pre-set-affiliation' event, allowing to block change or modify data
Matthew Wild <mwild1@gmail.com> [Tue, 16 Nov 2021 11:41:08 +0000] rev 11911
MUC: Add 'muc-pre-set-affiliation' event, allowing to block change or modify data
Mon, 15 Nov 2021 16:11:03 +0000 MUC: Add option to include form in registration query
Matthew Wild <mwild1@gmail.com> [Mon, 15 Nov 2021 16:11:03 +0000] rev 11910
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 <username/> 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.
Mon, 15 Nov 2021 13:31:06 +0100 mod_admin_shell: Handle absence of connection in security column (thanks arcseconds)
Kim Alvefur <zash@zash.se> [Mon, 15 Nov 2021 13:31:06 +0100] rev 11909
mod_admin_shell: Handle absence of connection in security column (thanks arcseconds) I surmise this can happen in a disconnected/smacks hibernation state.
Sat, 13 Nov 2021 22:12:39 +0100 mod_pubsub: Fix traceback in disco of non-existent node (thanks Martin)
Kim Alvefur <zash@zash.se> [Sat, 13 Nov 2021 22:12:39 +0100] rev 11908
mod_pubsub: Fix traceback in disco of non-existent node (thanks Martin) In this case `ret` is a table not containing the node, which makes pubsub_error_reply() try to get an error template with that `ret` table as index, which returns a `nil` then passed to table.unpack, which in turn throws the error.
Sat, 13 Nov 2021 13:32:43 +0100 net.connect: Prefer last connection error over last resolver error
Kim Alvefur <zash@zash.se> [Sat, 13 Nov 2021 13:32:43 +0100] rev 11907
net.connect: Prefer last connection error over last resolver error E.g. "connection refused" over one IP version instead of NoError for the other IP version.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip