Mercurial > prosody-modules
view mod_blocking/README.markdown @ 2044:06faf7a149e3
mod_poke_strangers: Log details about JIDs that look like they are spamming.
author | Thijs Alkemade <me@thijsalkema.de> |
---|---|
date | Fri, 05 Feb 2016 11:23:13 +0100 |
parents | 4d73a1a6ba68 |
children | 836b36d8bfd2 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'XEP-0191: Simple Communications Blocking support' ... 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](https://prosody.im/doc/modules/mod_blocklist). Configuration ============= Simply ensure that mod\_privacy (or mod\_privacy\_lists in 0.10+) and mod\_blocking are loaded in your modules\_enabled list: modules_enabled = { -- ... "privacy", -- or privacy_lists in Prosody 0.10+ "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 ------ ---------------------------------------------