1782
|
1 #summary XEP-0191: Simple Communications Blocking support
|
|
2 #labels Stage-Alpha
|
|
3
|
|
4 = Introduction =
|
|
5
|
|
6 Privacy lists are a widely implemented protocol for instructing your server on blocking communications with selected users and services.
|
|
7
|
|
8 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.
|
|
9
|
|
10 Such a protocol would also allow much simpler user interface design than the current attempts at full privacy list interfaces.
|
|
11
|
|
12 = Details =
|
|
13
|
|
14 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).
|
|
15
|
|
16 An XEP-0191 implementation without dependency on mod_privacy is available in Prosody 0.10 as [https://prosody.im/doc/modules/mod_blocklist mod_blocklist].
|
|
17
|
|
18 = Configuration =
|
|
19 Simply ensure that mod_privacy (or mod_privacy_lists in 0.10+) and mod_blocking are loaded in your modules_enabled list:
|
|
20
|
|
21 {{{
|
|
22 modules_enabled = {
|
|
23 -- ...
|
|
24 "privacy", -- or privacy_lists in Prosody 0.10+
|
|
25 "blocking",
|
|
26 -- ...
|
|
27 }}}
|
|
28
|
|
29 = Compatibility =
|
|
30 ||0.10||Works but will conflict with mod_blocklist||
|
|
31 ||0.9||Works||
|
|
32 ||0.8||Works||
|
|
33 ||0.7||Works||
|
|
34 ||0.6||Doesn't work|| |