Mercurial > prosody-modules
annotate mod_privacy_lists/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 25 Apr 2023 18:09:08 +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 ------ ------- |