Mercurial > libervia-backend
view doc/libervia-cli/blocking.rst @ 4247:4aa62767f501
plugin app manager: various improvements:
- Generated password must now be named and are stored, so they are re-used on following
restarts. Password size can now be specified.
- New `not` filter for `!libervia_param` to inverse a boolean value.
- Former `front_url` field has been renamed to `web_url_path` as it is the URL path used
for web frontend. All Web frontend related field are prefixed with `web_`.
- `front_url` is now used to specify a whole front URL (notably useful if an app uses its
own domain). A list can be used to retrieve a key, like for `url_prefix`, and `https`
scheme is added if no scheme is specified.
- An abstract class is now used for App Managers.
- Last application start time is stored in persistent data.
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 31 May 2024 11:08:14 +0200 |
parents | 29380ef68dbe |
children |
line wrap: on
line source
.. _libervia-cli_blocking: =========================== blocking: entities blocking =========================== ``blocking`` are commands to block or unblock users by their JIDs (as specified by `XEP-0191`_). You server must implement this XEP to use those commands. A blocking is usually done using bare JID, however, you may specify a resource if you want to block only this resource, or a domain if you want to block a whole domain. Please check `XEP-0191 § JID Matching`_ for details. list ==== List already blocked users. examples -------- Check who has already been blocked:: $ li blocking list block ===== Block one or more entities by specifying their JIDs. You just need to specify the bare JIDs of users that you want to block as positional argument, specify only a domain if you want to block a whole domain. examples -------- Louise wants to block ``spammer@example.com`` and the whole domain ``spammers.example``:: $ li blocking block spammer@example.com spammers.example unblock ======= ``unblock`` works the same way as ``block``. If you want to unblock all blocked users at once, you can use the ``all`` keyword. In this case, you'll have to confirm the action. If you don't want to confirm manually, you can use the ``-f, --force`` flag. examples -------- Pierre wants to unblock the domain ``example.com`` that he has blocked earlier:: $ li blocking unblock example.com Élysée want to unblock all blocked users, without confirmation:: $ li blocking unblock -f all .. _XEP-0191: https://xmpp.org/extensions/xep-0191.html .. _XEP-0191 § JID Matching: https://xmpp.org/extensions/xep-0191.html#matching