Mercurial > libervia-backend
view doc/libervia-cli/pubsub_node_affiliations.rst @ 3888:aa7197b67c26
component AP gateway: AP <=> XMPP reactions conversions:
- Pubsub Attachments plugin has been renamed to XEP-0470 following publication
- XEP-0470 has been updated to follow 0.2 changes
- AP reactions (as implemented in Pleroma) are converted to XEP-0470
- XEP-0470 events are converted to AP reactions (again, using "EmojiReact" from Pleroma)
- AP activities related to attachments (like/reactions) are cached in Libervia because
it's not possible to retrieve them from Pleroma instances once they have been emitted
(doing an HTTP get on their ID returns a 404). For now those cache are not flushed, this
should be improved in the future.
- `sharedInbox` is used when available. Pleroma returns a 500 HTTP error when ``to`` or
``cc`` are used in a direct inbox.
- reactions and like are not currently used for direct messages, because they can't be
emitted from Pleroma in this case, thus there is no point in implementing them for the
moment.
rel 371
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Wed, 31 Aug 2022 17:07:03 +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