Mercurial > libervia-backend
view doc/jp/identity.rst @ 3219:2ba602aef90e
plugin attach, aesgcm: attachments refactoring:
attachment handling has been simplified, and now use a "register" method similar as the
ones used for download or upload.
A default method (for unencrypted messages) will try a simple upload and will copy the
links to body.
AESGCM plugin has been adapted to be used for encrypted files. If more than one file is
sent with AESGCM plugin, they will be split in several messages as current de-facto
standard (OMEMO media sharing) doesn't support several files per message.
author | Goffi <goffi@goffi.org> |
---|---|
date | Wed, 18 Mar 2020 20:25:02 +0100 |
parents | 72583524cfd3 |
children | 6cf4bd6972c2 |
line wrap: on
line source
============================= identity: identity management ============================= Identity use several XMPP extensions (like vcards) to retrieve or set informations about an entity. For now it's really basic and only nickname and avatar are managed. get === Retrieve informations about the identity behind an XMPP entity. You only have to specify the jid of the entity, and you'll get (if set) his/her/its nickname and a link to the cached avatar. example -------- Get identity information about an entity:: $ jp identity get somebody@example.org set === Set identity data to the server, using various XMPP extensions. You set the data to change using ``-f KEY VALUE, --field KEY VALUE``, where ``KEY`` can only be ``nick`` at the moment. example ------- Set the nickname of default profile:: $ jp identity set -f nick toto