File

mod_conversejs: Serve base app at / This makes things slightly less awkward for the browser to figure out which URLs belong to a PWA. The app's "start URL" was previously without the '/' and therefore was not considered within the scope of the PWA. Now the canonical app URL will always have a '/'. Prosody/mod_http should take care of redirecting existing links without the trailing / to the new URL. If you have an installation at https://prosody/conversejs then it is now at https://prosody/conversejs/ (the first URL will now redirect to the second URL if you use it). The alternative would be to make the PWA scope include the parent, i.e. the whole of https://prosody/ in this case. This might get messy if other PWAs are provided by the same site or Prosody installation, however.

---
summary: 'XEP-0502 (MUC Activity Indicator) implementation'
...

This module provides an implementation of [XEP-0502 (MUC Activity Indicator)](https://xmpp.org/extensions/xep-0502.html) for Prosody.

To enable it, load it on a MUC host, for example:

```lua
Component "chat.domain.example" "muc"
    modules_enabled = { "muc_activity" }
```

When this module is loaded, it will expose the average number of messages per hour for all public MUCs.
The number is calculated over a 24 hour window.

Note that this module may impact server performance on servers with many MUCs.