aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/muc
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2019-10-20 01:20:11 +0200
committerKim Alvefur <zash@zash.se>2019-10-20 01:20:11 +0200
commite48914fdd7c3cda40e4d995abb2b67175a02d9d2 (patch)
tree2aa2b4d2b60fb454bb1224e01369846ec32534de /plugins/muc
parent0007aa04f11e9712247da1c15fbdc4f654a36534 (diff)
downloadprosody-e48914fdd7c3cda40e4d995abb2b67175a02d9d2.tar.gz
prosody-e48914fdd7c3cda40e4d995abb2b67175a02d9d2.zip
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.
Diffstat (limited to 'plugins/muc')
-rw-r--r--plugins/muc/register.lib.lua2
1 files changed, 0 insertions, 2 deletions
diff --git a/plugins/muc/register.lib.lua b/plugins/muc/register.lib.lua
index 21cb3f2f..95ed1a84 100644
--- a/plugins/muc/register.lib.lua
+++ b/plugins/muc/register.lib.lua
@@ -48,8 +48,6 @@ module:hook("muc-set-affiliation", function (event)
event.room._reserved_nicks = nil;
end);
-module:add_feature("jabber:iq:register");
-
module:hook("muc-disco#info", function (event)
event.reply:tag("feature", { var = "jabber:iq:register" }):up();
end);