Mercurial > prosody-modules
annotate mod_privacy_lists/README.markdown @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
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 ------ ------- |