List of IM platforms and protocols - TelepathyIM/wiki GitHub Wiki
Open or documented protocols
GSM
- Telepathy CM (Qt): telepathy-ofono (see also: Fragmentation story s01e03)
- Telepathy CM (glib): telepathy-ring
SIP
- Telepathy CM (glib): telepathy-rakia
- Telepathy CM (Qt): telepathy-resiprocate
XMPP (Jabber)
- Telepathy CM (Qt): telepathy-nonsense
- Telepathy CM (glib): telepathy-gabble
- Protocol description: https://xmpp.org/extensions
Telegram (MTProto)
- Telepathy CM (Qt): telepathy-morse
- Protocol description: https://core.telegram.org
Delta Chat
- Telepathy CM: https://code.ur.gs/lupine/telepathy-padfoot/
- Protocol description: https://github.com/deltachat/deltachat-core-rust/blob/master/spec.md
- Notable KDE/Qt client implementation: https://git.sr.ht/~link2xt/kdeltachat
Matrix (Riot)
- Telepathy CM (Qt): telepathy-tank
- Protocol description: https://matrix.org/docs/spec
IRC
- Telepathy CM (glib): telepathy-idle
- Protocol description: http://www.irchelp.org/protocol/rfc
Gitter
- Telepathy CM: does not exist
- Protocol description: https://developer.gitter.im/docs/messages-resource
Slack
- Telepathy CM: does not exist
- Protocol description: https://api.slack.com/messaging
Tox
- Telepathy CM (Vala): telepathy-poison
- Protocol description: https://toktok.ltd/spec.html
VK.com
- Telepathy CM: does not exist
- Protocol description: https://vk.com/dev/messages
Mattermost
- Telepathy CM: does not exist
- Protocol description: https://api.mattermost.com
Mumble
- Telepathy CM: does not exist
- Official client source code: github.com/mumble-voip/mumble (C++/Qt)
Rocket.Chat
- Telepathy CM: does not exist
- Protocol description: https://rocket.chat/docs/developer-guides/rest-api/chat
Briar
- Telepathy CM: does not exist
- Protocol description: https://code.briarproject.org/briar/briar-spec
Proprietary and/or adverse protocols
The purpose of the section is to show that Telepathy IM project participants know about mentioned protocols existence or even thought about supporting them but faced non-technical issues.
The morning sun never lasts a day, and licensing politics is not an exception for that principle. While protocols and platforms licensing and business models issues are not the task for Telepathy IM project itself, it could be handy to monitor proprietary and adverse protocols too.
Moreover, it's always a question of time and other resources to reverse engineer needed solutions if somebody is brave enough.
WhatsApp / Instagram / Facebook
WhatsApp / Instagram third-party clients are not permitted, and it is permanently banning those who continue to do so.
Discord
While Discord has Developer Portal with API Documentation and claims they love open source, their public API is available for bots only. No known plans about opening custom clients registration.