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

.. _libervia-cli_file_share_affiliations:

=============================================================
file/share/affiliations: file sharing affiliations management
=============================================================

``affiliations`` let you manage access permission to your shared files repository, in a
way similar as for pubsub.

Affiliations with file sharing are not standard and will only work with the Libervia file
sharing component.

Affiliations are similar to pubsub ones:

``owner``
  Has full permissions on the node, including changing affiliations. Owner can't be
  changed at the moment.

``publisher``
  Can read, upload and delete files

``member``
  Can access file but can't modify them or add new ones

``none``
  Is not a member of this node, use it to remove an existing affiliation.


get
===

Retrieve entities affiliated to this file sharing node, and their role

example
-------

Get affiliations of a file sharing node::

  $ li file share affiliations get -P "/some/path" louise@files.example.org

set
===

Set affiliations of an entity to a file sharing node.

examples
--------

Allow read access to a photo album to Louise::

  $ li file share affiliations set -c files.example.net -P "/albums/holidays" -a louise@tazar2.int member

Remove access to a directory from an old address of Pierre, and give it to the new one::

  $ li file share affiliations set -c files.example.net -N "some_namespace" -P
  "/interesting/directory" -a pierre@example.com none -a pierre@example.org member