Mercurial > libervia-backend
view doc/libervia-cli/avatar.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 | 267e4987b58b |
children |
line wrap: on
line source
=============================== avatar: retrieve/upload avatars =============================== Avatars are images associated to an XMPP entity. Several XMPP extensions are in use, Libervia tries to hide the technical details so avatar are as easy as possible to manipulate for end-user. get === Retrieve the avatar of the given entity. Entity jid is specified as positional argument. If an avatar is found, a path to its cached file is printed. Please note that this is the cache used by all Libervia ecosystem, **do not modify the cached image**. You may use it for read-only access, or copy it if you want to modify the image. You may use the ``-s, --show`` argument to display the found avatar. The software used to display the image can be specified in Libervia configuration (cf. :ref:`configuration`), in the ``[li]`` section: the ``image_cmd`` setting let you specify the path to the software. If ``image_cmd`` is not used, ``li`` will try some common software, and if none is found, it will try to open the image in a browser (which may sometimes result in using the default image software of the platform). When available, cached avatar is returned by defaut. If you want to ignore the cache, use the ``--no-cache`` option (of course this can result in more network requests). example ------- Get the avatar of ``louise@example.org`` and display it:: $ li avatar get --show louise@example.org set === Upload and set the given avatar for the profile. The only required argument is the path to the image to use as avatar. example ------- Set the avatar of the default profile:: $ li avatar set ~/photos/some_photo.jpg