Generated by GPT-5-mini| Telepathy (software) | |
|---|---|
| Name | Telepathy |
| Developer | Collabora Online, Red Hat, Intel Corporation |
| Released | 2006 |
| Programming language | C (programming language), GLib, D-Bus |
| Operating system | Linux, FreeBSD, OpenBSD |
| License | GNU General Public License |
Telepathy (software) is a modular real-time communication framework originally developed for instant messaging and presence that provides a unified abstraction for multiple network protocols and backends from disparate projects such as GStreamer, PulseAudio, GNOME Project, KDE, Mozilla Foundation, XMPP Standards Foundation, Freedesktop.org. It exposes service-oriented interfaces built on interprocess communication used by clients like Empathy (software), Kopete, Pidgin, Franz (software), and integrates with desktop environments including GNOME, KDE Plasma, Xfce. Telepathy is designed to separate protocol implementations from user-facing applications, enabling reuse by projects such as Mozilla Thunderbird, Evolution (software), Riot.im (now Element (software)), and enterprise systems like OpenSUSE deployments.
Telepathy provides a set of reusable components and standardized interfaces for presence, messaging, contact list management, voice, video, and file transfer that connect to multiple protocols developed by organizations like Jabber/XMPP, SIP Forum, Matrix (protocol), and vendors such as Microsoft Corporation, Cisco Systems. It is implemented using technologies from Freedesktop.org and D-Bus to allow desktop and server software across distributions like Debian, Ubuntu, Fedora, Arch Linux to interoperate. Major contributors include developers from Collabora Online, Red Hat, Intel Corporation, and community contributors from projects like GNOME Project and KDE e.V..
Telepathy's architecture separates concerns into components such as ConnectionManagers, Tubes, Channels, and Clients. ConnectionManagers implement protocol stacks with influences from projects like libpurple, SIP, XMPP Standards Foundation. Channels provide abstractions for MessageChannel, StreamChannel, and Channel types useful to clients including Empathy (software), Kopete, and Pidgin. Tubes provide inter-client communication influenced by technologies from D-Bus and X11, enabling features that integrate with toolkits like GTK+ and Qt (software). Core libraries such as Mission Control and AccountManagers coordinate registration and lifecycle management inspired by architectural patterns in Systemd, NetworkManager, and Avahi.
Telepathy supports backends for protocols including XMPP Standards Foundation, Session Initiation Protocol, MSNP (Microsoft Notification Protocol), IRC, and ICQ. ConnectionManager implementations like Gabble (for XMPP), Salut (for link-local), and Salut-inspired modules draw on libraries such as libnice, libsrtp, and GStreamer for media transport. Transport backends interoperate with projects such as Jingle extensions, RTP, DTLS, and standards bodies like the IETF and W3C that influence media negotiation and NAT traversal techniques found in implementations by Google LLC and Mozilla Foundation.
Telepathy provides presence, roster management, one-to-one and group messaging, voice and video calls, file transfer, and opaque data channels. These features are used by desktop clients like Empathy (software), Kopete, Pidgin, and by integration layers in Evolution (software), Mozilla Thunderbird, and Kontact from KDE e.V.. Media pipelines leverage GStreamer and PulseAudio for capture and playback while codecs and encryption draw from standards maintained by IETF, Opus (audio format), VP8, and implementations by FFmpeg. Advanced integrations include Screen sharing influenced by X.Org Foundation and remote desktop protocols used by VNC and SPICE.
Clients and integrations span desktop and mobile ecosystems. Notable clients include Empathy (software), Kopete, Pidgin, Franz (software), and integrations into GNOME Shell, KDE Plasma, and Xfce Panel. Telepathy libraries have been incorporated into projects such as Evolution (software), Mozilla Thunderbird, Kontact, and enterprise solutions like Red Hat Enterprise Linux toolchains. Developers use toolkits and libraries such as GTK+, Qt (software), libpurple, and services like D-Bus and PolicyKit to build secure, policy-aware clients.
Telepathy's development began in the mid-2000s with contributors from Intel Corporation, Collabora Online, and Red Hat aiming to unify messaging on Linux desktops to compete with proprietary ecosystems led by Microsoft Corporation and services from Google LLC. Key milestones include integration with GNOME Project around Empathy, adoption by KDE e.V. through Kopete hooks, support for XMPP Standards Foundation features via Gabble, and implementation of real-time media with GStreamer pipelines. The project evolved alongside initiatives from Freedesktop.org, standards work at the IETF, and multimedia improvements in PulseAudio and PipeWire.
Telepathy's security posture depends on protocol implementations and cryptographic libraries such as GnuTLS, OpenSSL, and standards from the IETF like TLS and SRTP. Privacy considerations are influenced by interoperable protocols including XMPP Standards Foundation, Matrix (protocol), and end-to-end encryption efforts from projects such as OMEMO, OTR (cryptography), and initiatives by Open Whisper Systems. Deployments interact with platform services like SELinux, AppArmor, and authentication frameworks exemplified by Kerberos and OAuth (protocol) when integrated into enterprise environments such as Red Hat Enterprise Linux or distributions like Debian.
Category:Instant messaging software