*** Bug 25407 has been marked as a duplicate of this bug. ***

This does not work yet with:
telepathy-filesystem-0.0.2-1.fc12.noarch
telepathy-idle-0.1.5-1.fc12.i686
libtelepathy-0.3.3-3.fc12.i686
telepathy-glib-0.9.0-1.fc12.i686
python-telepathy-0.15.11-1.fc12.noarch
empathy-2.28.2-2.fc12.i686
telepathy-farsight-0.0.12-1.fc12.i686
telepathy-glib-devel-0.9.0-1.fc12.i686
telepathy-butterfly-0.5.3-2.fc12.noarch
telepathy-gabble-0.8.9-3.fc12.i686
telepathy-salut-0.3.10-1.fc12.i686
telepathy-haze-0.3.1-3.fc12.i686
empathy-libs-2.28.2-2.fc12.i686
telepathy-mission-control-5.2.6-1.fc12.i686
telepathy-sofiasip-0.5.19-1.fc12.i686

As I read haze is just a wrapper around libpurple, so essentially the functionality should already be there?

telepathy-haze needs code for each supported libpurple feature, to map that feature into the Telepathy API (this isn't always possible without improving libpurple first, due to assumptions made by the libpurple API that aren't actually true for Haze).

This has already been done for (for instance) basic presence, the roster and IMs, but not for file transfers. When it's done, this bug will be closed.

*** Bug 27209 has been marked as a duplicate of this bug. ***

Any progress on this?

I would love to know if there is any progress on this... lack of aim file transfer is a huge issue in comparison to other IM clients.

*** Bug 50005 has been marked as a duplicate of this bug. ***

We agreed on IRC (Rob, sjoerd, wjt and myself) that a good enough solution could be easily implemented like that:

let purple write to a /tmp file, then haze stream that file to handler who write to final location.

Not elegant, but at least it won't block on more spec changes.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-haze/issues/22.