Mercurial > libervia-backend
view doc/libervia-cli/file_share_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 | 267e4987b58b |
children |
line wrap: on
line source
.. _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