File

mod_nodeinfo2/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parent 3830:63d8072dc864
child 4595:bac3dae031ee
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 Works
  0.11  Should work
  ----- -----------