view doc/jp/identity.rst @ 3060:730bbed77a89

plugin XEP-0045: join / MAM history improvements: - fixed use of history_d deferred so MAM history is stored in database as soon as possible and in right order - get MAM history with pages of 20 messages instead of 100 - if a message can't be parsed, an error message is logged (with a dump of the stanza), and the message is ignored, avoiding a crash and the impossibility the join the room at all - a new `mucRoomPrepareJoin` signal, containing room jid and profile, is sent when a room joining is started, this allow better UX as the frontend can show the room immediately, and lock it with a waiting message until it is fully available. The `mucRoomJoined` is still sent when the room is fully joined/avaiable, meaning that the frontend can unlock it and let the user interact with it
author Goffi <goffi@goffi.org>
date Fri, 18 Oct 2019 14:45:07 +0200
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