Mercurial > libervia-backend
view doc/libervia-cli/pubsub_node_affiliations.rst @ 3728:b15644cae50d
component AP gateway: JID/node ⟺ AP outbox conversion:
- convert a combination of JID and optional pubsub node to AP actor handle (see
`getJIDAndNode` for details) and vice versa
- the gateway now provides a Pubsub service
- retrieve pubsub node and convert it to AP collection, AP pagination is converted to RSM
- do the opposite: convert AP collection to pubsub and handle RSM request. Due to
ActivityStream collection pagination limitations, some RSM request produce inefficient
requests, but caching should be used most of the time in the future and avoid the
problem.
- set specific name to HTTP Server
- new `local_only` setting (`True` by default) to indicate if the gateway can request or
not XMPP Pubsub nodes from other servers
- disco info now specifies important features such as Pubsub RSM, and nodes metadata
ticket 363
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Tue, 25 Jan 2022 17:54:06 +0100 |
| parents | c80a0f864b5d |
| children |
line wrap: on
line source
.. _libervia-cli_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:: $ li 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:: $ li pubsub node affiliations set -n some_whitelisted_node -a louise@example.net publisher -a pierre@example.net member