view doc/jp/bookmarks.rst @ 3254:6cf4bd6972c2

core, frontends: avatar refactoring: /!\ huge commit Avatar logic has been reworked around the IDENTITY plugin: plugins able to handle avatar or other identity related metadata (like nicknames) register to IDENTITY plugin in the same way as for other features like download/upload. Once registered, IDENTITY plugin will call them when suitable in order of priority, and handle caching. Methods to manage those metadata from frontend now use serialised data. For now `avatar` and `nicknames` are handled: - `avatar` is now a dict with `path` + metadata like `media_type`, instead of just a string path - `nicknames` is now a list of nicknames in order of priority. This list is never empty, and `nicknames[0]` should be the preferred nickname to use by frontends in most cases. In addition to contact specified nicknames, user set nickname (the one set in roster) is used in priority when available. Among the side changes done with this commit, there are: - a new `contactGet` bridge method to get roster metadata for a single contact - SatPresenceProtocol.send returns a Deferred to check when it has actually been sent - memory's methods to handle entities data now use `client` as first argument - metadata filter can be specified with `getIdentity` - `getAvatar` and `setAvatar` are now part of the IDENTITY plugin instead of XEP-0054 (and there signature has changed) - `isRoom` and `getBareOrFull` are now part of XEP-0045 plugin - jp avatar/get command uses `xdg-open` first when available for `--show` flag - `--no-cache` has been added to jp avatar/get and identity/get - jp identity/set has been simplified, explicit options (`--nickname` only for now) are used instead of `--field`. `--field` may come back in the future if necessary for extra data. - QuickContactList `SetContact` now handle None as a value, and doesn't use it to delete the metadata anymore - improved cache handling for `metadata` and `nicknames` in quick frontend - new `default` argument in QuickContactList `getCache`
author Goffi <goffi@goffi.org>
date Tue, 14 Apr 2020 21:00:33 +0200
parents 72583524cfd3
children
line wrap: on
line source

============================
bookmarks: get/set bookmarks
============================

Bookmarks are links to MUC rooms or URLs with a few metadata. Due to historical reasons,
XMPP has several ways to handle bookmarks, and SàT handle them as transparently as
possible.

With SàT there are 3 places where you can get/store your bookmarks:

local
  the bookmarks is stored only locally in the database of SàT. It won't be available to
  other devices.
private
  the bookmarks use the old private XML storage (`XEP-0049`_). It is not recommended to
  use this if PubSub storage is available
pubsub
  the bookmarks use PEP storage (`XEP-0223`_), this is the currently recommended way to
  store bookmarks.

When possible, you can specify ``auto`` to let SàT choose the best location (i.e.
``pubsub`` if available, then ``private`` then ``local`` if nothing else is possible).

.. _XEP-0049: https://xmpp.org/extensions/xep-0049.html
.. _XEP-0223: https://xmpp.org/extensions/xep-0223.html


list
====

Get and print available bookmarks. You specify the location of the bookmarks to print
using ``-l {all,local,private,pubsub}, --location {all,local,private,pubsub``, by default
all bookmarks from all locations are printed.

Use ``-t {muc,url}, --type {muc,url}`` to indicate if you want to print MUC bookmarks or
URLs.

After printing the bookmarks location, the bookmarks will show the name and location (jid
for MUC or URL). For MUC bookmarks you'll also see nickname, and a star (``*``) if
autojoin is set.


examples
--------

Retrieve all MUC bookmarks::

  $ jp bookmarks list

Retrieve all bookmarked URL stored in PubSub::

  $ jp bookmarks list -l pubsub -t url


remove
======

Delete a bookmark. You need to specify the jid of the MUC room or the URL to remove as
positional argument. If you are deleting an URL, you need to specify it with ``-t url``

By default a confirmation is requested, use ``-f, --force`` if you don't want it (with
usual caution).

examples
--------

Delete the bookmark of a MUC room that you are not following anymore::

  $ jp bookmarks remove some_old_room@conference.example.net

Delete the bookmark of a URL without requesting confirmation::

  $ jp bookmarks remove -t url https://unused_url.example.net


add
===

Create or update a bookmark. The bookmark itself (URL or JID of the MUC) is specified as
positional argument. If you are bookmarking an URL, you need to specify it with ``-t
url``. A name is often helpful, use ``-n NAME, --name NAME`` to specify it.

For MUC only, you can specify the nick to use on the room with ``-N NICK, --nick NICK``,
and the flag ``-a, --autojoin`` indicates if you want to join the chat room automatically
when you're connecting.

If you're using add on a jid/URL which already exists, the metadata will be updated.

examples
--------

Add a bookmark to Salut à Toi official chat room::

  $ jp bookmarks add sat@chat.jabberfr.org -a

Add a link to Salut à Toi official website::

  $ jp bookmarks add -t url https://www.salut-a-toi.org -n "SàT officiel"