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.

Description
===========

This module lists those users, who **have** used their account in a
defined time-frame, basically the inverse of [mod_list_inactive].

Dependencies
============

[mod_lastlog] must be enabled to collect the data used by this module.

Usage
=====

    prosodyctl mod_list_active example.com time [format]

Time is a number followed by 'day', 'week', 'month' or 'year'

Formats are:

  --------- ------------------------------------------------
  default   `user@example.com`
  event     `user@example.com last action`
  --------- ------------------------------------------------

Example
=======

    prosodyctl mod_list_active example.com 1year

Help
====

    prosodyctl mod_list_active