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.

---
labels:
- 'Stage-alpha'
summary: Save received chat markers into MUC archives'
...

Introduction
============

Chat markers (XEP-0333) specification states that markers _SHOULD_ be
archived.  This is already happening in one to one conversations in
the personal archives but not in Group Chats.  This module hooks the
_muc-message-is-historic_ event to customize the `mod_muc_mam`
behavior and have the chat markers archived.

Usage
=====

First copy the module to the prosody plugins directory.

Then add "muc\_mam\_markers" to your `modules\_enabled` list in your
MUC component's definition.

No configuration options are available.