Software /
code /
prosody-modules
File
mod_lastlog2/README.markdown @ 4989:b74d592df9e2
mod_http_muc_log: Remove dead code
This might be something left over since a different variant where the
loop went like `for n = i-1, i-100, -1 do ... end` i.e. it went trough a
fixed number of items instead of all the page until the current message.
Then it would have needed something to stop going over the end, but
since the checks are simple it shouldn't be much of a problem looping
over even a very busy day.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 16 Aug 2022 01:27:59 +0200 |
parent | 4012:fd582067c732 |
child | 5900: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*