Mercurial > libervia-backend
view doc/jp/pubsub_node_affiliations.rst @ 3231:e756e0eb1be4
core (memory/encryption): automatic start encryption if peer send encrypted message:
If peer sends encrypted message and we have no encryption activated, we automatically
start encryption to avoid sending plain text message when answering.
markAsEncrypted now needs the encryption algorithm namespace as mandatory argument.
author | Goffi <goffi@goffi.org> |
---|---|
date | Mon, 23 Mar 2020 17:52:18 +0100 |
parents | 72583524cfd3 |
children |
line wrap: on
line source
.. _jp-pubsub_node_affiliations: ======================================================= pubsub/node/affiliations: nodes affiliations management ======================================================= ``affiliations`` is a subcommand handling the affiliations of a node (not to be confused with ``pubsub affiliations`` which handle the affiliations of a PubSub service). get === Retrieve entities affiliated to this node and their role. example ------- Get affiliations of a node:: $ jp pubsub node affiliations get -n some_node set === Set affiliation of an entity on a node. Affiliations are specified with ``-a JID AFFILIATION`` argument. Check `XEP-0060 affiliations`_ for allowed values for ``AFFILIATION``. Use ``none`` to remove an affiliation. .. _XEP-0060 affiliations: https://xmpp.org/extensions/xep-0060.html#affiliations example ------- If we have a whitelisted node ``some_whitelisted_node``, we can allow ``louise@example.net`` to publish on it (by setting her role as ``publisher``), and ``pierre@example.net`` to access it (by setting his role as ``member``) using the following command:: $ jp pubsub node affiliations set -n some_whitelisted_node -a louise@example.net publisher -a pierre@example.net member