Mercurial > libervia-backend
view doc/libervia-cli/blocking.rst @ 4212:5f2d496c633f
core: get rid of `pickle`:
Use of `pickle` to serialise data was a technical legacy that was causing trouble to store
in database, to update (if a class was serialised, a change could break update), and to
security (pickle can lead to code execution).
This patch remove all use of Pickle in favour in JSON, notably:
- for caching data, a Pydantic model is now used instead
- for SQLAlchemy model, the LegacyPickle is replaced by JSON serialisation
- in XEP-0373 a class `PublicKeyMetadata` was serialised. New method `from_dict` and
`to_dict` method have been implemented to do serialisation.
- new methods to (de)serialise data can now be specified with Identity data types. It is
notably used to (de)serialise `path` of avatars.
A migration script has been created to convert data (for upgrade or downgrade), with
special care for XEP-0373 case. Depending of size of database, this migration script can
be long to run.
rel 443
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 23 Feb 2024 13:31:04 +0100 |
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