Mercurial > prosody-modules
view mod_csi_muc_priorities/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | 562d3b219876 |
children |
line wrap: on
line source
# Introduction This module lets users specify which of the group chats they are in are less important. This influences when [mod_csi_simple][doc:modules:mod_csi_simple] decides to send stanzas vs waiting until there is more to send. Users in many large public channels might benefit from this. # Configuration The module is configured via ad-hoc an command called *Configure group chat priorities* that should appear in the menus of compatible clients. The command presents a form that accepts a list of XMPP addresses. Currently there is a single priority, *Lower priority*, which is suitable for e.g. noisy public channels. mod_csi_simple considers groupchat messages important by default on the assumptions that smaller and more important private chats are more common among most users. A message of type groupchat from an address in this list will not be considered important enough to send it to an inactive client, unless it is from the current user or mentions of their nickname. **Note** that mention support require the separate module [mod_track_muc_joins] to also be loaded. ``` {.lua} modules_enabled = { -- other modules etc "csi_simple", "csi_muc_priorities", "track_muc_joins", -- optional } ```