Mercurial > prosody-modules

view mod_privacy_lists/README.markdown @ 5264:d3ebaef1ea7a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_oauth2: Correctly verify OAuth client credentials on revocation Makes no sense to validate against username and password here, or using a token to revoke another token, or itself? In fact, upon further discussion, why do you need credentials to revoke a token? If you are not supposed to have the token, revoking it seems the most responsible thing to do with it, so it should be allowed, while if you are supposed to have it, you should be allowed to revoke it.
author Kim Alvefur <zash@zash.se>
date Tue, 21 Mar 2023 21:57:18 +0100
parents 7c90e8a67a4f
children 9f41d2d33e3e
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: 'Privacy lists (XEP-0016) support'
...

Introduction
------------

Privacy lists are a flexible method for blocking communications.

Originally known as mod\_privacy and bundled with Prosody, this module
is being phased out in favour of the newer simpler blocking (XEP-0191)
protocol, implemented in [mod\_blocklist][doc:modules:mod_blocklist].

Configuration
-------------

None. Each user can specify their privacy lists using their client (if
it supports XEP-0016).

Compatibility
-------------

  ------ -------
  0.9    Works
  0.10   Works
  ------ -------