Telepathy Glossary

Translation of the original in Catalan. Read it in: CatalàCastellano

Part 3 of 6XMPP
  1. XMPP: introduction
  2. XMPP with BOSH: using HTTP as a transport protocol
  3. Telepathy Glossary
  4. Articles about XMPP
  5. VNC session with TCP proxy over XMPP
  6. XMPP tools

First of all, a short introduction to: What is

Telepathy

?

It is a framework that unifies different real-time communication systems. It uses DBUS as the communication interface between applications.

Advantages of Telepathy:

  • Real time: it supports IM systems (one-to-one and groups), video calls and voice calls.
  • Unified: it allows different applications to take advantage of the system's capabilities simultaneously and to work collaboratively.
  • Framework: it dissects the communication system into small parts and makes them as simple as it can, so that using them together the communication process is as simple as possible.

The glossary of terms, in a few words what you have to keep in mind and remember when we talk about Telepathy.

  • MUC (multi user chat): also called a chat room, or chat channel.
  • Mission Control: responsible for managing messaging accounts: creating connections and maintaining the presence states of contacts.
  • Glabbe: it is a Jabber connection manager.
  • Tapioca: it is a framework for VoIP and IM applications. It supports SIP/XMPP.
  • Farsight: the same as Tapioca, but aimed at video conferencing.
  • Stream Engine: it exports Farsight's functions to DBUS, and vice versa.
  • Tubes: it is the mechanism Telepathy uses to support data transfer between remote applications, that is: remote IPC. The idea behind it is "if two people connected to an IM service can talk, why shouldn't two applications connected to an IM be able to exchange information?".
  • Stream Tubes: it is a transport method used by Telepathy, very similar to SOCK_STREAM sockets: ordered and reliable packet delivery.
  • IB (in-band): when the 'Tubes' use the messaging server to exchange data. This system can be very slow to carry certain kinds of information, for example, VNC sessions.
  • OOB (out of band): the data 'Tubes' use different paths outside the XMPP network, for example, direct connections between peers over UDP or TCP.
  • Empathy: it is an IM client written using the Telepathy libraries.
  • XEP-0095 Stream Initiation: this specification defines an XMPP extension that starts data streams between two entities connected to the XMPP network. The protocol supports the possibility of including metadata about the data stream to be exchanged.
  • XEP-0065 SOCKS5 bytestreams abstract: an XMPP extension is defined to establish OOB connections between two peers; the connection between the peers can be direct or through a SOCKS5 proxy. In principle the idea is to use TCP for this kind of link, although it could also work over UDP.
  • **XEP-0163 PEP **(Personal Eventing Protocol): it defines the semantics of a protocol that, using XMPP's publish-subscribe features, broadcasts state and presence changes. In this way we can make an account's state work as if it were a pubsub service; simplifying the possibility of subscribing to data and notifications associated with that account. An example, to make it easier to understand: we can have a calendar service that warns us that we have to do certain things if we are available, but if we are away instead it makes no sense for it to warn us.
  • XEP-0080 User Location: it is an extension that allows sending information about the user's geographical position.