Mercurial > prosody-modules
view mod_nodeinfo2/README.markdown @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parents | bac3dae031ee |
children | 694b62d8a82f |
line wrap: on
line source
--- description: labels: 'Stage-Alpha' --- Introduction ============ This module exposes a [nodeinfo2](https://git.feneas.org/jaywink/nodeinfo2) .well-known URL for use e.g. from [the-federation.info](https://the-federation.info). Configuration ============= Enable the `nodeinfo` module in your global `modules_enabled` section: ``` modules_enabled = { ... "nodeinfo2" ... } ``` Set the `nodeinfo2_expose_users` option to false if you don’t want to expose statistics about the amount of users you host: ``` nodeinfo2_expose_users = false ``` Set the `nodeinfo2_expose_posts` option to false if you don’t want to expose statistics about the amount of messages being exchanged by your users: ``` nodeinfo2_expose_posts = false ``` This module depends on [mod\_lastlog](https://modules.prosody.im/mod_lastlog.html) to calculate user activity, and [mod\_http](https://prosody.im/doc/http). Most of its configuration actually happens in this dependency. Compatibility ============= ------- -------------------- trunk Does not work [^1] 0.11 Should work ------- -------------------- [^1]: not after [5f15ab7c6ae5](https://hg.prosody.im/trunk/rev/5f15ab7c6ae5)