Mercurial > libervia-backend
view doc/libervia-cli/blocking.rst @ 4240:79c8a70e1813
backend, frontend: prepare remote control:
This is a series of changes necessary to prepare the implementation of remote control
feature:
- XEP-0166: add a `priority` attribute to `ApplicationData`: this is needed when several
applications are working in a same session, to know which one must be handled first.
Will be used to make Remote Control have precedence over Call content.
- XEP-0166: `_call_plugins` is now async and is not used with `DeferredList` anymore: the
benefit to have methods called in parallels is very low, and it cause a lot of trouble
as we can't predict order. Methods are now called sequentially so workflow can be
predicted.
- XEP-0167: fix `senders` XMPP attribute <=> SDP mapping
- XEP-0234: preflight acceptance key is now `pre-accepted` instead of `file-accepted`, so
the same key can be used with other jingle applications.
- XEP-0167, XEP-0343: move some method to XEP-0167
- XEP-0353: use new `priority` feature to call preflight methods of applications according
to it.
- frontend (webrtc): refactor the sources/sink handling with a more flexible mechanism
based on Pydantic models. It is now possible to have has many Data Channel as necessary,
to have them in addition to A/V streams, to specify manually GStreamer sources and
sinks, etc.
- frontend (webrtc): rework of the pipeline to reduce latency.
- frontend: new `portal_desktop` method. Screenshare portal handling has been moved there,
and RemoteDesktop portal has been added.
- frontend (webrtc): fix `extract_ufrag_pwd` method.
rel 436
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sat, 11 May 2024 13:52:41 +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