Mercurial > prosody-modules
view mod_muc_block_pm/mod_muc_block_pm.lua @ 6167:886c985ece61
mod_lastlog2: Skip initializing internal API (and storage) in prosodyctl
Initializing storage in the global context under prosodyctl causes the
module.command to fail to execute because the storage module has already
been loaded.
Introduced in 7b722955c59b
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sat, 08 Feb 2025 14:12:18 +0100 |
| 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);
