Mercurial > libervia-backend
view doc/libervia-cli/pubsub_attachments.rst @ 3934:e345d93fb6e5
plugin OXPS: OpenPGP for XMPP Pubsub implementation:
OpenPGP for XMPP Pubsub (https://xmpp.org/extensions/inbox/pubsub-encryption.html,
currently a protoXEP) is implemented and activated when `encrypted` is set to `True` in
pubsub's `extra` data.
On item retrieval, the decryption is transparent if the key is known, except if the
`decrypt` key in `extra` is set to `False` (notably useful when one wants to checks that
data is well encrypted).
Methods and corresponding bridge methods have been implemented to manage shared secrets
(to share, revoke or rotate the secrets).
plugin XEP-0060's `XEP-0060_publish` trigger point as been move before actual publish so
item can be modified (here e2ee) by the triggers. A new `XEP-0060_items` trigger point has
also been added.
`encrypted` flag can be used with plugin XEP-0277's microblog data
rel 380
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sat, 15 Oct 2022 20:36:53 +0200 |
| parents | 8b76caa89aa0 |
| children |
line wrap: on
line source
.. _libervia-cli_pubsub_attachments: ======================================================= pubsub/attachments: (Un)Attach Metadata to Pubsub Items ======================================================= ``attachments`` is a subcommand grouping all pubsub commands related to "pubsub attachments" specification. With them, you can (un)attach data to any pubsub item. This is notably used to handle data like saying if an item is (un)noticed, or add emoji reactions. get === Retrieve a list of all attached data to an item. By default all attachments of the item are returned, this can be filtered by using ``-j JIDS, --jid JIDS`` example ------- Louise check all attachments on her last blog post:: $ li pubsub attachments get -s louise@example.org -n urn:xmpp:microblog:0 -i some-news-acf0 set === Update or replace attachments. By default new attachments are updated, but if the ``-R, --replace`` is used, new attachments replace the whole former one where it make sense. For instance, ``-R`` doesn't change anything for ``noticed`` attachments, but it will replace all reactions (potentially with no reaction at all), where the default behaviour is to merge former and new reactions. Note that only specified attachments are affected, if unknown or unspecified attachments exist, they will stay unmodified. For now, only ``noticed`` (to say that an element has been seen and taken into account) and ``reactions`` (emojis to show emotion or other kind of reaction about something) are managed. ``-N [BOOLEAN], --noticed [BOOLEAN]`` takes on optional argument to say if the item is noticed or not. If the optional argument is not specified, if will be the same as if the ``true`` value was used. examples -------- Pierre wants to indicate to Louise that is has seen and he took into account her last blog post:: $ li pubsub attachments set -s louise@example.org -n urn:xmpp:microblog:0 -i some-news-acf0 -N Louise wants to react to Pierre blog post about night trains:: $ li pubsub attachments set -s pierre@example.net -n urn:xmpp:microblog:0 -i nigh-train-are-great-f120 -r 🚆🌜💤