Mercurial > prosody-modules
view mod_muc_config_restrict/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 | 34fb3d239ac1 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Restrict MUC configuration options to server admins ... Introduction ============ Sometimes, especially on public services, you may want to allow people to create their own rooms, but prevent some options from being modified by normal users. For example, using this module you can prevent users from making rooms persistent, or making rooms publicly visible. Details ======= You need to supply a list of options that will be restricted to admins. Available options can vary, but the following table lists Prosody's built-in options (as defined in XEP-0045): Name Description --------------------------------- ------------------------------------------- muc\#roomconfig\_roomname The title/name of the room muc\#roomconfig\_roomdesc The description of the room muc\#roomconfig\_persistentroom Whether the room should remain when empty muc\#roomconfig\_publicroom Whether the room is publicly visible muc\#roomconfig\_changesubject Whether occupants can change the subject muc\#roomconfig\_whois Control who can see occupant's real JIDs muc\#roomconfig\_roomsecret The room password muc\#roomconfig\_moderatedroom Whether the room is moderated muc\#roomconfig\_membersonly Whether the room is members-only muc\#roomconfig\_historylength The length of the room history Some plugins may add other options to the room config (in Prosody 0.10+), for which you will need to consult their documentation for the full option name. Configuration ============= Enable the plugin on a MUC host (do not put it in your global modules\_enabled list): ``` {.lua} Component "conference.example.com" "muc" modules_enabled = { "muc_config_restrict" } muc_config_restricted = { "muc#roomconfig_persistentroom"; -- Prevent non-admins from changing a room's persistence setting "muc#roomconfig_membersonly"; -- Prevent non-admins from changing whether rooms are members-only } ``` Compatibility ============= ------- -------------- trunk Doesn't work (uses is_admin) 0.12 Works? ------- --------------