Mercurial > prosody-modules
view mod_lastlog2/README.markdown @ 4188:4611999fd8d3
mod_muc_batched_probe: don't rely on mt_room:respond_to_probe method
That method assumes it's responding to a `<presence>` stanza, which breaks for
the bached probe use-case.
author | JC Brand <jc@opkode.com> |
---|---|
date | Mon, 12 Oct 2020 13:21:16 +0200 |
parents | fd582067c732 |
children | c5df6d53f17f |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Record last timestamp of events --- # Introduction Similar to [mod_lastlog], this module records the last timestamp of various events, but keeps the last timestamp per type of event, instead of the last event. # Usage As with all modules, copy it to your plugins directory and then add it to the modules\_enabled list: ``` {.lua} modules_enabled = { -- other modules "lastlog2", } ``` # Configuration There are some options you can add to your config file: Name Type Default Description ---------------------- --------- --------- --------------------------------- lastlog\_ip\_address boolean false Log the IP address of the user? # Usage You can check a user's last activity by running: prosodyctl mod_lastlog username@example.com # Compatibility Version State --------- ------- Any *TBD*