Mercurial > prosody-modules
annotate mod_privacy_lists/README.markdown @ 4989:b74d592df9e2
mod_http_muc_log: Remove dead code
This might be something left over since a different variant where the
loop went like `for n = i-1, i-100, -1 do ... end` i.e. it went trough a
fixed number of items instead of all the page until the current message.
Then it would have needed something to stop going over the end, but
since the checks are simple it shouldn't be much of a problem looping
over even a very busy day.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 16 Aug 2022 01:27:59 +0200 |
parents | 7c90e8a67a4f |
children | 9f41d2d33e3e |
rev | line source |
---|---|
1803 | 1 --- |
2 labels: | |
3 - 'Stage-Beta' | |
4 summary: 'Privacy lists (XEP-0016) support' | |
5 ... | |
6 | |
7 Introduction | |
8 ------------ | |
9 | |
10 Privacy lists are a flexible method for blocking communications. | |
11 | |
12 Originally known as mod\_privacy and bundled with Prosody, this module | |
13 is being phased out in favour of the newer simpler blocking (XEP-0191) | |
2237
7c90e8a67a4f
mod_privacy_lists/README: Link to mod_blocklist
Kim Alvefur <zash@zash.se>
parents:
1894
diff
changeset
|
14 protocol, implemented in [mod\_blocklist][doc:modules:mod_blocklist]. |
1803 | 15 |
16 Configuration | |
17 ------------- | |
18 | |
19 None. Each user can specify their privacy lists using their client (if | |
20 it supports XEP-0016). | |
21 | |
22 Compatibility | |
23 ------------- | |
24 | |
25 ------ ------- | |
26 0.9 Works | |
27 0.10 Works | |
28 ------ ------- |