[Telepathy] future of Telepathy?

Daniel Pocock daniel at pocock.pro
Mon Apr 25 14:00:22 UTC 2016

On 25 April 2016 15:41:20 CEST, Dominik George <nik at naturalnet.de> wrote:
>> With my GNOME hat on, we are not spending much effort on our instant
>> messaging features. For a free software desktop, XMPP was by far the
>> most useful and mature part of Telepathy. Google, Facebook and
>> Microsoft has either moved away from XMPP or deprecated it, while
>> Telegram and Whatsapp use something different.
>WhatsApp uses XMPP. It is slightly modified to force people to use the 
>official client, but it is XMPP.
>> None of the XMPP-based free VoIP options ever worked reliably. They
>> were spotty at best.
>That was years ago. Look at Jitsi, the Jitsi video bridge and Jitsi
>The main issue with XMPP-based VoIP is client implementations.
>XMPP-VoIP never 
>worked reliably in Telepathy because Telepathy's implementation of
>is horrible.
>I don't mean to be rude, and I think the Telepathy developers sure do a
>job, but please do not blame it on XMPP itself.

Unfortunately, the problems faced in this area are an example of fragmentation in the free software community.  There are people doing great things with the Linux desktop and there are people doing great things with free, open source VoIP (e.g. the WebRTC stacks in Firefox and Chrome are very effective at NAT traversal), we need to reach a little further to join the dots an get all these things together.

>> Given how hard it is to support any of the popular instant messaging
>> networks, a free software IM stack looks increasingly pointless.
>> someone will come up with a mature Telegram implementation ...
>Given the above, please all stop whining and start get Telepathy back
>track, thus bringing XMPP forward by providing another well-working
>instead of bringing support for proprietary protocols forward!

How about having Ring, Tox and Matrix connection managers?



More information about the telepathy mailing list