(with the exception of mainland China[...]).
-snip
I don't know how this affects use of MSN via Microsoft's Live Connect
XMPP bridge (announced last December) and telepathy-gabble, which is
what you get if you add a Windows Live account in GNOME Online Accounts.
My pessimistic assumption
protocols. Empathy is the
default chat client in GNOME, and is based on the Telepathy framework,
making it easier for other GNOME applications to integrate collaboration
functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Dependencies:
• gee-0.8
this?
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
30caeb664105af6a854fb2811d61843d1591593660f545d0c08613e9e41eaaf4
folks-0.9.0.tar.xz
libfolks 0.9.0 — He's heating up!
=
Libfolks pulls together contacts from any number of accounts supported
by the libfolks backends. This release includes a number of backends,
including Telepathy, evolution
102b1867355d16e73a837871a058dda13c74fa385908ddda1623893ab0baee4a
folks-0.9.1.tar.xz
libfolks 0.9.1 — Impeccable Timing
==
Libfolks pulls together contacts from any number of accounts supported
by the libfolks backends. This release includes a number of backends,
including Telepathy, evolution
telepathy-skykit is connection manager which implements integration
layer between skypekit (Skype embedded SDK) and telepathy.
https://github.com/max-posedon/telepathy-skykit
It is kind of proof-of-concept, only 1:1 chat, contact list works.
Implementation is based on telepathy-python
telepathy-foo is a connection manager which implements simple echo behavior.
https://github.com/max-posedon/telepathy-foo
It is kind of proof-of-concept. Implementation is based on
telepathy-python with patches
https://github.com/max-posedon/telepathy-python
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Thanks to Debarshi Ray
the whole contact list and display it in this menu?
That doesn't seem to scale to me, but if that's what you really want see
this example: telepathy-glib/examples/client/python/contact-list.py
Note that this will fetch all the contacts from Telepathy but what you
actually want is probably to fetch
The chicken legs release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-logger/telepathy-logger-0.8.0.tar.bz2
signature:
http://telepathy.freedesktop.org/releases/telepathy-logger/telepathy-logger-0.8.0.tar.bz2.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-logger
...@gmail.com wrote:
Hi all.
I have been running python scripts for telepathy-gabble communication;
and following are the observations ::
a)
Client :: Fedora-17
Server :: ejabberd on CentOS
In this case, I am able to register the users on the server; and receive
the members changed signals
Hi Ying-Chun Liu,
Vala bindings are usually generated automatically through GObject
introspection. Telepathy Logger should support GObject introspection. It
can be activated at build time using --enable-introspection. If you
encounter any issues, please file bug:
https://bugs.freedesktop.org
the notification in
the bottom opens, not the chatwindow. I think it could be an extra
option in the preferences of empathy.
Is someone already doing this, so I can help him, or can someone help me?
Thanks in advance,
David Magnus Henriques
___
telepathy
this error for the past days. If it
happens again, I'll save the logs.
Thank you for your time :)
--
Pedro
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
their certificate needs to have
that as its CN or as one of its alternative names.
This should affect non-Telepathy clients equally: if a client is
unaffected, then either it's talking to an unaffected server (they use
multiple servers with geolocation, so it's not necessarily the case that
all their servers
that on Fedora 17,
telepathy-gabble crashed on going offline, thus losing the tray icons
with unread messages.
Any chance to have a trace of this crash?
Hi!
I think this was the bug I submitted the crash to:
https://bugzilla.redhat.com/show_bug.cgi?id=828797 .
Since I've upgraded to Fedora
Hi all.
I have been running python scripts for telepathy-gabble communication; and
following are the observations ::
a)
Client :: Fedora-17
Server :: ejabberd on CentOS
In this case, I am able to register the users on the server; and receive
the members changed signals (as per the attached
Hi all.
I have been running python scripts for telepathy-gabble communication; and
following are the observations ::
a)
Client :: Fedora-17
Server :: ejabberd on CentOS
In this case, I am able to register the users on the server; and receive
the members changed signals (as per the attached
Another note ::
d)
The client (Fedora-17) is running the exact same python-script, during
every test with either of the server.
On Fri, Jan 18, 2013 at 1:14 AM, Ajay Garg ajaygargn...@gmail.com wrote:
Hi all.
I have been running python scripts for telepathy-gabble communication
protocols. Empathy is the
default chat client in GNOME, and is based on the Telepathy framework,
making it easier for other GNOME applications to integrate collaboration
functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Dependencies:
• telepathy
Hi all.
I have experience in setting up a Hello World program for
telepathy-salut; using this program, buddies are able to see other, and get
notified upon arrivals and departures of buddies (from salut connection
that is).
I believe that the same program can be ported with minimal efforts
protocols. Empathy is the
default chat client in GNOME, and is based on the Telepathy framework,
making it easier for other GNOME applications to integrate collaboration
functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
This stable release fixes
Hi,
On 07/01/13 12:44, Simon McVittie wrote:
On 06/01/13 19:12, Maksim Melnikau wrote:
[PATCH 1/3] fix checkValidProtocolName test in BaseConnection
This patch looks reasonable, but I'm out of touch with telepathy-qt, so
someone who is active on that project should review merge it. Please
On Mon, Jan 7, 2013 at 2:28 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
If you insist on using telepathy-python and want to add modern Telepathy
features to it, I would ask you to demonstrate those features working
correctly when prototyped in a connection manager anyway, before
.
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
On 06/01/13 12:06, Maksim Melnikau wrote:
2. if program segfaults - it has a bug, always, there is now excuse
for it, programs shouldn't segfault on non-correct data
I agree: the usual Telepathy rule is don't be crashable by someone on
the other side of D-Bus, even if they're wrong. I've
On 06/01/13 12:23, Maksim Melnikau wrote:
I basically agree with you, but I think it requires few commits before
death, to make it a bit compatible with current telepathy-glib, just
because popular distros won't remove it in near future.
Debian 7, currently in freeze, no longer has telepathy
On 06/01/13 19:12, Maksim Melnikau wrote:
[PATCH 1/3] fix checkValidProtocolName test in BaseConnection
This patch looks reasonable, but I'm out of touch with telepathy-qt, so
someone who is active on that project should review merge it. Please
consider opening a bug (bugs.freedesktop.org
/vxWowCgloSMfcqLlSj5S0+wFxK9FZAw
w3IAn1TjAn8Y68Erb03l2j6V8I291kka
=92U9
-END PGP SIGNATURE-
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
On Mon, Jan 7, 2013 at 11:24 AM, Guillaume Desmottes
guillaume.desmot...@collabora.co.uk wrote:
Le mercredi 02 janvier 2013 à 16:04 +, Pedro Francisco a écrit :
This seems to have been made worse by the fact that on Fedora 17,
telepathy-gabble crashed on going offline, thus losing the tray
Le dimanche 06 janvier 2013 à 02:01 +0300, Maksim Melnikau a écrit :
tp_simple_client_factory_ensure_contact returns NULL for protocols, if
tp_connection_has_immortal_handles=0. Right now its happened for any
telepathy-python based protocols (butterfly, sunsine, mixer).
when
Le vendredi 04 janvier 2013 à 20:59 +0300, Maksim Melnikau a écrit :
Is it possible to have updated telepathy-specs (xml, _generated python
files, etc) in next telepathy-python release? (e.g. do it in master
soon)
I don't think we should update telepathy-python anymore. That would be
sending
On Sun, Jan 6, 2013 at 12:44 PM, Xavier Claessens xclae...@gmail.com wrote:
Le dimanche 06 janvier 2013 à 02:01 +0300, Maksim Melnikau a écrit :
telepathy-python is dead and all CM based on it as well. Lots of newer
client-side API in telepathy-glib assume that the CM implements newer
spec
On Sun, Jan 6, 2013 at 12:51 PM, Xavier Claessens xclae...@gmail.com wrote:
Le vendredi 04 janvier 2013 à 20:59 +0300, Maksim Melnikau a écrit :
I don't think we should update telepathy-python anymore. That would be
sending a false signal that it is still usable.
I basically agree with you
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
, if I understand correctly.
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
tp_simple_client_factory_ensure_contact returns NULL for protocols, if
tp_connection_has_immortal_handles=0. Right now its happened for any
telepathy-python based protocols (butterfly, sunsine, mixer).
when tp_simple_client_factory_ensure_contact returns NULL
-import magic
-
def usage():
print %s FILE % sys.argv[0]
print FILE is a path to the location you want the file saved to
--
1.8.1
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
Hello,
I've just installed the telepathy-sofiasip-package (version 0.7.1-2).
Everything works fine untill I try to have a call. I can phone somebody
and he can answer the call but then their is no sound at all. Same thing
if the other person try to call me. I can answer it, but there's also
Is it possible to have updated telepathy-specs (xml, _generated python
files, etc) in next telepathy-python release? (e.g. do it in master
soon)
I could send a patch, but its quite big, and useless.
Yes, I know telepathy-python is deprecated, but now (as I understand)
there is no other variants
: www.siblog.ishans.info
Ishan's way: www.blog.ishans.info
-
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
Il giorno dom, 30/12/2012 alle 23.51 +0300, Maksim Melnikau ha scritto:
diff --git a/src/server/conn.py b/src/server/conn.py
I applied and pushed upstream both of these patches. Thanks!
--
Jonny Lamb
___
telepathy mailing list
telepathy
Il giorno lun, 31/12/2012 alle 02.59 +0300, Maksim Melnikau ha scritto:
+ $(srcdir)/run.c $(srcdir)/run.h \
In the past we've avoided adding Telepathy-GLib service files available
for g-i for various reasons, the biggest of which being that it wouldn't
work as Telepathy-GLib exposes dbus
.: clicking pause on empathy-debugger seems not to be working.
Thanks in Advance,
--
Pedro
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
File /usr/lib64/python2.7/site-packages/telepathy/server/conn.py,
line 172, in create_handle
handle = Handle(id, handle_type, name)
NameError: global name 'handle_type' is not defined
% pyflakes src/server/conn.py
src/server/conn.py:172: undefined name 'handle_type'
src/server/conn.py:173
):
object_path=object_path)
def Close(self):
-raise telepathy.NotImplemented(Contact lists can't be closed)
+raise NotImplemented(Contact lists can't be closed)
from telepathy._generated.Channel_Type_File_Transfer \
--
1.8.0.2
Signed-off-by: Maksim Melnikau maxpose...@gmail.com
---
telepathy-glib/introspection.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/telepathy-glib/introspection.am b/telepathy-glib/introspection.am
index 4789942..6a79a10 100644
--- a/telepathy-glib/introspection.am
+++ b/telepathy-glib
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Dependencies:
• geocode
On 13/12/12 19:57, Spoon Reloaded wrote:
We will retire Messenger in all countries worldwide in the first
quarter of 2013 (with the exception of mainland China[...]).
Does that mean Telepathy will no longer work for MSN (outside of China)?
I would assume so, but we probably won't know
of MSN via Microsoft's Live Connect
XMPP bridge (announced last December) and telepathy-gabble, which is
what you get if you add a Windows Live account in GNOME Online Accounts.
My pessimistic assumption is that this will also cease to work; but
we'll see.
Completely guessing here: since Skype
http://blogs.skype.com/en/2012/11/skypewlm.html
We will retire Messenger in all countries worldwide in the first
quarter of 2013 (with the exception of mainland China where Messenger
will continue to be available).
Does that mean Telepathy will no longer work for MSN (outside of China
certificate, but for the wrong server name. Their
documentation[1] says the server's official name (and the one we should
connect to) is messenger.live.com, so their certificate needs to have
that as its CN or as one of its alternative names.
This should affect non-Telepathy clients equally: if a client
-Telepathy clients equally: if a client is
unaffected, then either it's talking to an unaffected server (they use
multiple servers with geolocation, so it's not necessarily the case that
all their servers have this error), or it's not validating certificates
properly (a security flaw in that client
Hooray! Hooray! Hooray!
tarball:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.17.2.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.17.2.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-gabble
?
--
Pedro
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Bugs fixed:
- Fixed
This is the start of a new unstable branch. Don't swing on it too hard.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-haze/telepathy-haze-0.7.0.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-haze/telepathy-haze-0.7.0.tar.gz.asc
git: http
Wow, what a small number of fixes!
tarball:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.1.14.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.1.14.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-idle
attention in #telepathy!
Happy Friday,
--
Will
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
Here are some crash fixes, and a pretty important fix which means we can
talk to iChat again. (0.8 is the current stable branch of Salut.)
tarball:
http://telepathy.freedesktop.org/releases/telepathy-salut/telepathy-salut-0.8.1.tar.gz
signature:
http://telepathy.freedesktop.org/releases
Wow, what a lot of fixes!
tarball:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.1.13.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.1.13.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-idle
Enhancements
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
This stable release
guessing the unread buffer only works while the account is connected,
no?
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
and don't read them
* sudo wpa_cli terminate
* check that no unread messages are on 'systray'
Bug report on bugtracker soon(tm) if I get no answers.
Thanks in Advance!
--
Pedro
___
telepathy mailing list
telepathy@lists.freedesktop.org
http
as some protocol may let you get back those messages from
server in later connections (Skype as an example).
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
Here are some bugfixes!
tarball:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.16.4.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.16.4.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-gabble
Fixes
The world's slowest ticket machines release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.20.1.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.20.1.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy
the cache gets into a stale state.
OK. I've filed bgo#687671 - Add Individual aggregation cache
-Travis
smime.p7s
Description: S/MIME cryptographic signature
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman
, and then after a lot more profiling
work.
Philip
signature.asc
Description: This is a digitally signed message part
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
audibly already.
What does everyone think about that?
Regards,
-Travis
smime.p7s
Description: S/MIME cryptographic signature
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
tests should be added anyhow, but I would
vote against any significant changes to the aggregator that doesn't make
the aggregator tests exhaustive (and still pass them).
-Travis
smime.p7s
Description: S/MIME cryptographic signature
___
telepathy mailing
it in the DB.
See the reasoning above.
-Travis
smime.p7s
Description: S/MIME cryptographic signature
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
).
-Travis
smime.p7s
Description: S/MIME cryptographic signature
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
part
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
a
reputation for being unstable which I really don’t want perpetuated.
Amen to that.
G.
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
to be had in rearchitecting folks to optimise for the first query type
you mention.
Really? Telepathy backend certainly can load a single TpContact. EDS
backend can load a single EContact as well with
e_book_client_get_contact(), or does it internally load the whole thing?
You’re right
Good morning.
I am happy to report the release of telepathy-logger 0.6.0. This is the
start of a new stable branch, mainly sparked off by requiring a release
fixing introspection warnings, but not wanting to release with the
walker API yet.
tarball:
http://telepathy.freedesktop.org/releases
: 1) given an
individual
uid, give all its linked persona uid. 2) given a persona uid, give its
individual uid.
This means we have to define persona and individual uid:
* Persona uid: I suggest using N9 format:
telepathy://account path/contact-id,
eds://ESource id/EContact id
:
telepathy://account path/contact-id,
eds://ESource id/EContact id.
Or anything from which we can fetch a TpContact or EContact.
* Individual uid: there are 2 cases, does it have just one Persona or more?
- just one: use its persona uid.
- more than one: use a uuid and keep
is (for instance the roster XML for Gabble), or in a sqlite database or
something.
I don't think we really want to lock-in the roster is stored in
(XML|sqlite3) format at *this* location as part of the Telepathy API.
Even with the proposed Avatars redesign for 1.0, we've been able to
avoid locking
field. Again
this means that to figure out all the personas that belongs together you
need
to parse ALL vcards.
I'd be interested to hear why Folks doesn't already use a separate
lookaside database - I'm sure there must be a reason?
3) Telepathy backend does some obscure offline caching
one of them
always loaded in background.
Regards,
Xavier Claessens.
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
it in the vcard in EDS
achieves that (I can put it in Google Contacts). Having a separate
database breaks that property.
--
Olivier Crête
olivier.cr...@collabora.com
signature.asc
Description: This is a digitally signed message part
___
telepathy mailing
format
is (for instance the roster XML for Gabble), or in a sqlite database or
something.
I don't think we really want to lock-in the roster is stored in
(XML|sqlite3) format at *this* location as part of the Telepathy API.
Even with the proposed Avatars redesign for 1.0, we've been able to
avoid
think that solution has just far too
much disadvantages to counter the small benefit. If we have smart
auto-merging suggestions like Marco's plugin on N900 it's just a matter
of clicking yes merge them on all devices.
Regards,
Xavier Claessens.
___
telepathy
, so I'm not
making this up from nothing ;-)
Regards,
Xavier Claessens.
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
. The information about which personas belong in which
individuals could be cached.
3) Telepathy backend does some obscure offline caching. I'm not sure any app
actually use that, and I'm not even confident that works correctly.
gnome-contacts uses it to be able to list IM contacts when those IM
don’t think this is a feasible
approach.
Philip
signature.asc
Description: This is a digitally signed message part
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
this as well.
Finally, this discussion should be happening on the folks mailing list,
not the Telepathy one. I’ve CCed it in.
Philip
signature.asc
Description: This is a digitally signed message part
___
telepathy mailing list
telepathy
together you
need
to parse ALL vcards.
Not necessarily. The information about which personas belong in which
individuals could be cached.
Ah right, it can still be a keyfile, right?
3) Telepathy backend does some obscure offline caching. I'm not sure any app
actually use
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
Desmottes:
Le vendredi 05 octobre 2012 à 23:47 +0200, Rainer Dorsch a écrit :
I am struggling somewhat with the empathy logs. I can only select
Empathy.FileTransfer in the Empathy debug view. For reference I
uploaded some logs to
http://bokomoko.de/~rd/telepathy
. I can only select
Empathy.FileTransfer in the Empathy debug view. For reference I
uploaded some logs to
http://bokomoko.de/~rd/telepathy/
Looking at this log you are connected using kathrin.dor...@jabber.org
and receive a location from rdor...@jabber.org, but you say
debug view. For reference I uploaded
some logs to
http://bokomoko.de/~rd/telepathy/
Looking at this log you are connected using kathrin.dor...@jabber.org
and receive a location from rdor...@jabber.org, but you say that Empathy
doesn't display any location for rdor...@jabber.org
Le vendredi 05 octobre 2012 à 23:47 +0200, Rainer Dorsch a écrit :
I am struggling somewhat with the empathy logs. I can only select
Empathy.FileTransfer in the Empathy debug view. For reference I uploaded some
logs to
http://bokomoko.de/~rd/telepathy/
Looking at this log you
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
This new stable
protocols. Empathy is the default chat
client in GNOME, and is based on the Telepathy framework, making it easier for
other GNOME applications to integrate collaboration functionality.
You can visit the project web site:
http://live.gnome.org/Empathy
What's New?
===
Brown paper bag
601 - 700 of 4694 matches
Mail list logo
