prosody-modules
3e2e708fd18b
mod_muc_archive/README.markdown

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

File

mod_muc_archive/README.markdown @ 4581:3e2e708fd18b

mod_adhoc_dataforms_demo: Add compat with 0.11 (vs trunk api change) The name of the "access for anyone" permission level changed from "user" in 0.11 to "any" in 0.12/trunk to make it clearer that it's basically unrestricted. This is unfortunately not backwards-compatible. Thanks to Sam for stumbling upon this during a demo.
author Kim Alvefur <zash@zash.se>
date Tue, 01 Jun 2021 19:23:32 +0200
parent 3957:7e96b95924bd
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: Log MUC messages to disk
...

# Introduction

This module logs the conversations of chatrooms running on the server to Prosody's data store.

This is a fork of [mod_muc_log](https://modules.prosody.im/mod_muc_log.html) which uses the newer storage API.
This allows you to also log messages to a SQL backend.

## Changes between mod_muc_archive and mod_muc_log:

- Use newer module storage API so that you can also store in SQL
- Adhere to config option `muc_log_all_rooms` (also used by mod_muc_mam)
- Add affiliation information in the logged stanza
- Remove code that set (and then removed) an "alreadyJoined" dummy element

NOTE: The changes are unlikely to be entirely backwards compatible because the stanza
being logged is no longer wrapped with `<stanza time=...>`.

Details
=======

mod\_muc\_archive must be loaded individually for the components that need it.

Assuming you have a MUC component already running on
conference.example.org then you can add muc\_archive to it like so:

    Component "conference.example.org" "muc"
       modules_enabled = {
          "muc_archive";
       }


Compatibility
=============

  ------ -----
  0.11   Works
  ------ -----