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!

--
-- A module to indicate if a MUC message qualifies as historic based on XEP-0334 hints
--

module:depends"muc_mam"

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

module:hook("muc-message-is-historic", function (event)
  if (event.stanza:get_child("no-store", "urn:xmpp:hints") or
    event.stanza:get_child("no-permanent-store", "urn:xmpp:hints")) then
      module:log("debug", "Not archiving stanza: %s (urn:xmpp:hints)", event.stanza)
    return false
  elseif event.stanza:get_child("store", "urn:xmpp:hints") then
    return true
  else
    return nil
  end
end)