Mercurial > prosody-modules
view mod_muc_block_pm/mod_muc_block_pm.lua @ 5907:d194d1012fd3
Updating dox for mod_rest. Ideas expressed / clarified:
1) Making clear that mod_rest isn't to be installed under VirtualHosts AND as a component.
2) Understanding some of the implications of this choice:
A) Changes to user authentication
B) How it affects subdomains
3) More consistent use of domain names for clarity.
4) Using different heading sizes to show scope of section.
Essentially, I added all the tidbits I had to clarify in getting this to work in my
own example.
| author | Ben Smith <bens@effortlessis.com> |
|---|---|
| date | Mon, 13 May 2024 13:25:13 -0700 |
| parents | 67f7df9892bb |
| children |
line wrap: on
line source
local st = require "util.stanza"; module:hook("muc-disco#info", function(event) table.insert(event.form, { name = "muc#roomconfig_allowpm"; value = "moderators" }); end); module:hook("muc-private-message", function(event) local stanza, room = event.stanza, event.room; local from_occupant = room:get_occupant_by_nick(stanza.attr.from); if from_occupant and from_occupant.role == "moderator" then return -- moderators may message anyone end local to_occupant = room:get_occupant_by_nick(stanza.attr.to) if to_occupant and to_occupant.role == "moderator" then return -- messaging moderators is ok end if to_occupant.bare_jid == from_occupant.bare_jid then return -- to yourself is okay, used by some clients to sync read state in public channels end room:route_to_occupant(from_occupant, st.error_reply(stanza, "cancel", "policy-violation", "Private messages are disabled", room.jid)) return false; end, 1);
