Mercurial > prosody-modules

view mod_muc_mam_markers/mod_muc_mam_markers.lua @ 5264:d3ebaef1ea7a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_oauth2: Correctly verify OAuth client credentials on revocation Makes no sense to validate against username and password here, or using a token to revoke another token, or itself? In fact, upon further discussion, why do you need credentials to revoke a token? If you are not supposed to have the token, revoking it seems the most responsible thing to do with it, so it should be allowed, while if you are supposed to have it, you should be allowed to revoke it.
author Kim Alvefur <zash@zash.se>
date Tue, 21 Mar 2023 21:57:18 +0100
parents a1fc677d0cc8
children
line wrap: on
line source

-- mod_muc_mam_markers
--
-- Copyright (C) 2019 Marcos de Vera Piquero <marcos.devera@quobis.com>
--
-- This file is MIT/X11 licensed.
--
-- A module to make chat markers get stored in the MUC archives
--

module:depends"muc_mam"

local function handle_muc_message (event)
	local stanza = event.stanza;
	local is_received = stanza:get_child("received", "urn:xmpp:chat-markers:0");
	local is_displayed = stanza:get_child("displayed", "urn:xmpp:chat-markers:0");
	local is_acked = stanza:get_child("acknowledged", "urn:xmpp:chat-markers:0");
	if (is_received or is_displayed or is_acked) then
		return true;
	end
	return nil;
end

module:hook("muc-message-is-historic", handle_muc_message);

module:log("debug", "Module loaded");