Mercurial > prosody-modules
annotate mod_muc_lang/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 | 4e8b5ea7f4c2 |
children |
rev | line source |
---|---|
3075 | 1 # Introduction |
2 | |
3 This module adds support for advertising the language used in a room. | |
4 | |
5 # Configuring | |
6 | |
7 ``` {.lua} | |
8 Component "rooms.example.net" "muc" | |
9 modules_enabled = { | |
10 "muc_lang"; | |
11 } | |
12 ``` | |
13 | |
14 The room language is specified in a new field in the room configuration | |
15 dialog, accessible through compatible clients. | |
16 | |
17 Use [language codes](https://en.wikipedia.org/wiki/ISO_639) like `en`, | |
18 `fr`, `de` etc. | |
19 | |
20 # Compatibility | |
21 | |
22 Meant for use with Prosody 0.10.x | |
23 | |
24 Native support was [added in Prosody | |
25 trunk/0.11](https://hg.prosody.im/trunk/rev/9c90cd2fc4c3), so there is | |
26 no need for this module. |