Hi,
Thanks for responding. My use-case is similar to the nokia. I have a VOIP
phone
and I am integrating telepathy to enable gtalk calling. I do not
require contacts or their presence information. Just need a simple URI
dialing. I am not sure if I need mission control. But, will have a look at
Hi,
I couldn't find much information abt Telepathy-Qt4 anywhere online. So, didn't
give a try. May be that would suit my implementation more. Given my use-case do
you suggest to look at telepathy-qt4?
Thanks,
Sai
--- On Tue, 3/9/10, mikhail.zabal...@nokia.com mikhail.zabal...@nokia.com
Hi,
If your software platform already uses Qt, it makes sense to use Telepathy-Qt4
on the client side.
Otherwise, you are free to choose. There is also a Python binding, and the C
client-side interface based on GLib and provided by telepathy-glib.
Information on Telepathy-Qt4 is available,
Hi, this is Mikhail from Nokia.
-Original Message-
From: telepathy-boun...@lists.freedesktop.org [mailto:telepathy-
boun...@lists.freedesktop.org] On Behalf Of ext Edward Page
Sent: Wednesday, March 10, 2010 4:24 AM
To: Sjoerd Simons
Cc: telepathy@lists.freedesktop.org
Subject: Re:
The Beige Curtain release.
Homepage:
http://telepathy.freedesktop.org/wiki/Papyon
Tarball:
http://telepathy.freedesktop.org/releases/papyon/papyon-0.4.5.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/papyon/papyon-0.4.5.tar.gz.asc
The latest reviewed code is always available from:
The Objection release.
This release disables audio/video calls, which have been broken since
Microsoft removed the necessary servers.. Also note that it depends on
telepathy-python 0.15.16 and that we recommend the use of papyon 0.4.5
so password don't get displayed in butterfly's logs.
Tarball:
Hello folks.
Recently I was tasked with continuing the work that Dafydd started on
SASL. The good news is that this allows a more unified approach with the
SSL and other authentication schemes we have been working on,
specifically XTLS. The bad news is that I scratched a lot of the
previous work