Mercurial > prosody-modules
annotate mod_privacy_lists/README.markdown @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Mon, 22 Mar 2021 15:55:02 +0000 |
| parents | 7c90e8a67a4f |
| children |
| 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 ------ ------- |