Mercurial > prosody-modules
view mod_host_blacklist/mod_host_blacklist.lua @ 3656:3e0f4d727825
mod_vcard_muc: Add an alternative method of signaling avatar change
When the avatar has been changed, a signal is sent that the room
configuration has changed. Clients then do a disco#info query to find
the SHA-1 of the new avatar. They can then fetch it as before, or not if
they have it cached already.
This is meant to be less disruptive than signaling via presence, which
caused problems for some clients.
If clients transition to the new method, the old one can eventually be removed.
The namespace is made up while waiting for standardization.
Otherwise it is very close to what's described in
https://xmpp.org/extensions/inbox/muc-avatars.html
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 25 Aug 2019 20:46:43 +0200 |
parents | 547b3c05cc06 |
children |
line wrap: on
line source
local jid_split = require "util.jid".split; local st = require "util.stanza"; local set = require "util.set"; local select = select; local blacklist = module:get_option_inherited_set("host_blacklist", {}); local function stanza_checker(attr) return function (event) local host = select(2, jid_split(event.stanza.attr[attr])); if blacklist:contains(host) then module:send(st.error_reply(event.stanza, "cancel", "not-allowed", "Communication with this domain is restricted")); return true; end end end check_incoming_stanza = stanza_checker("from"); check_outgoing_stanza = stanza_checker("to"); for stanza_type in set.new{"presence","message","iq"}:items() do for jid_type in set.new{"bare", "full", "host"}:items() do module:hook("pre-"..stanza_type.."/"..jid_type, check_outgoing_stanza, 500); module:hook(stanza_type.."/"..jid_type, check_incoming_stanza, 500); end end