Mercurial > prosody-modules
view mod_muc_notifications/README.markdown @ 5461:06640647d193
mod_http_oauth2: Fix use of arbitrary ports in loopback redirect URIs
Per draft-ietf-oauth-v2-1-08#section-8.4.2
> The authorization server MUST allow any port to be specified at the
> time of the request for loopback IP redirect URIs, to accommodate
> clients that obtain an available ephemeral port from the operating
> system at the time of the request.
Uncertain if it should normalize the host part, but it also seems
harmless to treat IPv6 and IPv4 the same here.
One thing is that "localhost" is NOT RECOMMENDED because it can
sometimes be pointed to non-loopback interfaces via DNS or hosts file.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 17 May 2023 13:51:30 +0200 |
parents | 69219097aa85 |
children |
line wrap: on
line source
--- labels: - 'Stage-alpha' summary: 'Notify of MUC messages to not present members' ... Introduction ============ This module listens to MUC messages and sends a notification to the MUC members not present in the MUC at that moment. By default, the notification will be a message with a simple text as body. By sending this "out-of-MUC" notification, not-joined members will be able to know that new messages are available. Usage ===== First copy the module to the prosody plugins directory. Then add "muc\_notifications" to your modules\_enabled list in your MUC component: ```{.lua} Component "conference.example.org" "muc" modules_enabled = { "muc_notifications", } ``` You may also want to enable "offline\_hints" module so the notification messages sent by this module are not added to the offline storage for later delivery. Configuration ============= Option Description --------------------------- ---------------------------------------------------------------------------------------------- muc\_notification\_invite If set to `true`, the notification sent will take the form of a MUC invite. (default: `false`)