Mercurial > prosody-wiki
comparison mod_blocking.wiki @ 134:6abd50682378
Created wiki page through web user interface.
| author | MWild1 |
|---|---|
| date | Sun, 13 Jun 2010 08:43:20 +0000 |
| parents | |
| children | deb4182a7b61 |
comparison
equal
deleted
inserted
replaced
| 133:d7a9f3c69e49 | 134:6abd50682378 |
|---|---|
| 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 = Configuration = | |
| 17 Simply ensure that mod_privacy and mod_blocking are loaded in your modules_enabled list: | |
| 18 | |
| 19 {{{ | |
| 20 modules_enabled = { | |
| 21 -- ... | |
| 22 "privacy", | |
| 23 "blocking", | |
| 24 -- ... | |
| 25 }}} | |
| 26 | |
| 27 = Compatibility = | |
| 28 ||0.8||Works|| | |
| 29 ||0.7||Works|| | |
| 30 ||0.6||Doesn't work|| |