view doc/jp/identity.rst @ 3372:5d926c7b0d99

plugin app manager: first draft: /!\ new optional dependency: pyyaml this plugin manage the life cycle of external applications. Application handlers register to it. Data needed to launch an application as set in YAML files. Local data types are used to get values directly from SàT: - !sat_conf to retrieve a configuration value - !sat_generate_pwd to generate a password - !sat_param for parameters specified a launch Data can be exposed when an instance is launched, this can be used to specify the port (notably the one used for web), or a generated password.
author Goffi <goffi@goffi.org>
date Mon, 28 Sep 2020 21:10:30 +0200
parents 6cf4bd6972c2
children
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 data about the
avatar.

When available, cached values are 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 identity information about an entity::

  $ jp identity get somebody@example.org

set
===

Set identity data to the server, using various XMPP extensions. So far, you can only
change the nickname of an entity using ``-n, --nick`` or or more times

example
-------

Set 2 nicknames for default profile::

  $ jp identity set -n toto -n titi