Mercurial > prosody-modules
view mod_nodeinfo2/README.markdown @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
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)