Mercurial > libervia-backend
view doc/libervia-cli/avatar.rst @ 4044:3900626bc100
plugin XEP-0166: refactoring, and various improvments:
- add models for transport and applications handlers and linked data
- split models into separate file
- some type hints
- some documentation comments
- add actions to prepare confirmation, useful to do initial parsing of all contents
- application arg/kwargs and some transport data can be initialised during Jingle
`initiate` call, this is notably useful when a call is made with transport data (this is
the call for A/V calls where codecs and ICE candidate can be specified when starting a
call)
- session data can be specified during Jingle `initiate` call
- new `store_in_session` argument in `_parse_elements`, which can be used to avoid
race-condition when a context element (<decription> or <transport>) is being parsed for
an action while an other action happens (like `transport-info`)
- don't sed `sid` in `transport_elt` during a `transport-info` action anymore in
`build_action`: this is specific to Jingle File Transfer and has been moved there
rel 419
author | Goffi <goffi@goffi.org> |
---|---|
date | Mon, 15 May 2023 16:23:11 +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