view doc/libervia-cli/pubsub_attachments.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 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 🚆🌜💤