Mercurial > libervia-backend
view doc/libervia-cli/pubsub_node_affiliations.rst @ 3764:125c7043b277
comp AP gateway: publish, (un)subscribe/(un)follow, public subscription/following/followers:
this patch implements those major features:
- `publish` is implemented on virtual pubsub service, thus XMPP entities can now publish
to AP using this service
- replies to XMPP items are managed
- `inReplyTo` is filled when converting XMPP items to AP objects
- `follow` and `unfollow` (actually an `undo` activity) are implemented and mapped to
XMPP's (un)subscribe. On subscription, AP actor's `outbox` collection is converted to
XMPP and put in cache. Subscriptions are always public.
- `following` and `followers` collections are mapped to XMPP's Public Pubsub Subscription
(which should be XEP-0465, but the XEP is not yet published at the time of commit), in
both directions.
- new helper methods to check if an URL is local and to get JID from actor ID
doc will follow to explain behaviour
rel 365
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 13 May 2022 19:12:33 +0200 |
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