Mercurial > prosody-modules
view mod_blocking/README.md @ 6403:13c61a068c71
mod_pubsub_serverinfo: Include hostname in default pubsub node name
This change ensures that every host publishes to a unique node by default,
which is important when publishing info about multiple hosts.
The old default node name was "serverinfo"
The new default node name is in the format "serverinfo/example.com" where
example.com is automatically replaced by the publishing host's name.
This affects existing deployments in the following ways:
- If you already configured pubsub_serverinfo_node explicitly in your config,
then nothing will change, your current configuration will still be used.
- If you did not specify it in your config (i.e. used the default) then the
module will switch to publishing to the new node. If your configuration is
correct this shouldn't be noticed, because the new node will automatically
be created and configured by the module. If you want, you can clean up the
old 'serverinfo' node using:
prosodyctl shell pubsub delete_node pubsub.example.com serverinfo
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Wed, 11 Feb 2026 09:40:30 +0000 |
| parents | fe081789f7b5 |
| children |
line wrap: on
line source
--- labels: - Stage-Deprecated rockspec: dependencies: - mod_privacy_lists summary: "XEP-0191: Simple Communications Blocking support" --- ::: {.alert .alert-warning} This module is deprecated as it depends on the deprecated [mod_privacy_lists], use the core module [mod_blocklist][doc:modules:mod_blocklist] instead. ::: Introduction ============ Privacy lists are a widely implemented protocol for instructing your server on blocking communications with selected users and services. However experience has shown that the power and flexibility of the rule-based system that privacy lists allow is very often much more complex than the user needs, and that in most cases a simple block on all communications to or from a list of specified JIDs would suffice. Such a protocol would also allow much simpler user interface design than the current attempts at full privacy list interfaces. Details ======= Simple Communications Blocking was developed to solve the above issues, and allows the client to manage a simple list of blocked JIDs. This plugin implements support for that protocol in Prosody, however the actual blocking is still managed by mod\_privacy, so it is **required** for that plugin to be loaded (this may change in future). An XEP-0191 implementation without dependency on mod\_privacy is available in Prosody 0.10 as [mod\_blocklist][doc:modules:mod_blocklist]. Configuration ============= Simply ensure that [mod_privacy_lists] and mod_blocking are loaded in your modules_enabled list: modules_enabled = { -- ... "privacy_lists", "blocking", -- ... Compatibility ============= ------ --------------------------------------------- 0.10 Works but will conflict with mod\_blocklist 0.9 Works 0.8 Works 0.7 Works 0.6 Doesn't work ------ ---------------------------------------------