mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

--
-- 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)