Mercurial > libervia-backend
view doc/libervia-cli/blocking.rst @ 4044:3900626bc100
plugin XEP-0166: refactoring, and various improvments:
- add models for transport and applications handlers and linked data
- split models into separate file
- some type hints
- some documentation comments
- add actions to prepare confirmation, useful to do initial parsing of all contents
- application arg/kwargs and some transport data can be initialised during Jingle
`initiate` call, this is notably useful when a call is made with transport data (this is
the call for A/V calls where codecs and ICE candidate can be specified when starting a
call)
- session data can be specified during Jingle `initiate` call
- new `store_in_session` argument in `_parse_elements`, which can be used to avoid
race-condition when a context element (<decription> or <transport>) is being parsed for
an action while an other action happens (like `transport-info`)
- don't sed `sid` in `transport_elt` during a `transport-info` action anymore in
`build_action`: this is specific to Jingle File Transfer and has been moved there
rel 419
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Mon, 15 May 2023 16:23:11 +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