Software / code / prosody-modules
Annotate
mod_privacy_lists/README.markdown @ 5536:96dec7681af8
mod_firewall: Update user marks to store instantly via map store
The original approach was to keep marks in memory only, and persist them at
shutdown. That saves I/O, at the cost of potentially losing marks on an
unclean shutdown.
This change persists marks instantly, which may have some performance overhead
but should be more "correct".
It also splits the marking/unmarking into an event which may be watched or
even fired by other modules.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 08 Jun 2023 16:20:42 +0100 |
| parent | 2237:7c90e8a67a4f |
| child | 5859: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 ------ ------- |
