File

mod_conformance_restricted/mod_conformance_restricted.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
parent 1343:7dbde05b48a9
line wrap: on
line source

-- Prosody IM
-- Copyright (C) 2012 Florian Zeitz
--
-- This project is MIT/X11 licensed. Please see the
-- COPYING file in the source package for more information.
--

local st = require "util.stanza";
local jid = require "util.jid";

module:hook("message/host", function (event)
	local origin, stanza = event.origin, event.stanza;
	local node, host, resource = jid.split(stanza.attr.to);
	local body = stanza:get_child_text("body");

	if resource ~= "conformance" then
		return; -- Not interop testing
	end

	if body == "PI" then
		origin.send("<?testing this='out'?>");
	elseif body == "comment" then
		origin.send("<!-- no comment -->");
	elseif body == "DTD" then
		origin.send("<!DOCTYPE greeting [\n<!ENTITY test 'You should not see this'>\n]>");
	elseif body == "entity" then
		origin.send("<message type='chat' to='"..stanza.attr.from.."'><body>&test;</body></message>");
	else
		local reply = st.reply(stanza);
		reply:body("Send me one of: PI, comment, DTD, or entity");
		origin.send(reply);
	end

	return true;
end);