view mod_muc_mam_markers/mod_muc_mam_markers.lua @ 5390:f2363e6d9a64

mod_http_oauth2: Advertise the currently supported id_token signing algorithm This field is REQUIRED. The algorithm RS256 MUST be included, but isn't because we don't implement it, as that would require implementing a pile of additional cryptography and JWT stuff. Instead the id_token is signed using the client secret, which allows verification by the client, since it's a shared secret per OpenID Connect Core 1.0 ยง 10.1 under Symmetric Signatures. OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that are not supported here, but that's okay because this is served from the RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!
author Kim Alvefur <zash@zash.se>
date Sun, 30 Apr 2023 16:13:40 +0200
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");