prosody-modules
fe8222112cf4
mod_muc_restrict_pm/README.md
Software / code / prosody-modules
File
mod_muc_restrict_pm/README.md @ 6199:fe8222112cf4
mod_conversejs: Serve base app at /
This makes things slightly less awkward for the browser to figure out which
URLs belong to a PWA. The app's "start URL" was previously without the '/' and
therefore was not considered within the scope of the PWA. Now the canonical
app URL will always have a '/'.
Prosody/mod_http should take care of redirecting existing links without the
trailing / to the new URL.
If you have an installation at https://prosody/conversejs then it is now at
https://prosody/conversejs/ (the first URL will now redirect to the second
URL if you use it).
The alternative would be to make the PWA scope include the parent, i.e.
the whole of https://prosody/ in this case. This might get messy if other
PWAs are provided by the same site or Prosody installation, however.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 11 Feb 2025 13:18:38 +0000 |
| parent | 6079:8b6696bd9e40 |
line wrap: on
line source
--- labels: - 'Stage-Obsolete' summary: Limit who may send and recieve MUC PMs ... ::: {.alert .alert-warning} This feature has been merged into [mod_muc][doc:modules:mod_muc] in trunk and is therefore obsolete when used with a version >0.12.x or trunk. It can still be used with Prosody 0.12. ::: # Introduction This module adds configurable MUC options that restrict and limit who may send MUC PMs to other users. If a user does not have permissions to send a MUC PM, the MUC will send a policy violation stanza. # Setup ```lua Component "conference.example.org" "muc" modules_enabled = { "muc_restrict_pm"; } ``` Compatibility ============= version note --------- --------------------------------------------------------------------------- trunk [Integrated](https://hg.prosody.im/trunk/rev/47e1df2d0a37) into `mod_muc` 0.12 Works
