| 22 | | * Connect to protocols |
| 23 | | * Works, but needs a bit of work to make the connection have parameters for the options supported by the underlying prpl, and to make the parameters as far as possible match those used by other CMs. |
| 24 | | * Also, it'd be nice to report the actual reasons for unrequested disconnections. |
| 25 | | * ~~Text IM channels~~ |
| 26 | | * Done. Slight hiccup with /me on IRC, but I'm sure we'll survive, particularly since MUCs aren't implemented so IRC is a bit useless :-) |
| 27 | | * Contact lists |
| 28 | | * `HANDLE_TYPE_LIST`: Only the "subscribe" channel is implemented. Right now it's assumed that all protocols can store this stuff server-side; my reading of the spec suggests that this list should not exist if it can't be stored on the server, such as in IRC. |
| 29 | | * `HANDLE_TYPE_GROUP`: Working, with a small amount of surprising magic. When a contact is added to "subscribe", they mysteriously appear in the "Buddies" group (FIXME: they actually appear in _("Buddies")); if a buddy is removed from all groups, they fall off "subscribe" (FIXME: should they reappear in "Buddies" instead?). |
| 30 | | * Presence (status) |
| 31 | | * Protocols support statuses from available, busy, away, extended away, invisible, and offline presences, all but the latter two with a message, if a corresponding StatusType exists on the underlying prpl. |
| 32 | | * Ideally, each protocol would support at the Telepathy level exactly those status types which the prpl supports. |
| 33 | | * Aliasing |
| 34 | | * Retrieving remote aliases works |
| 35 | | * Saving remote aliases works where the prpl allows, and is not available otherwise |
| 36 | | * Setting your own alias is unimplemented because I haven't got around to adding API to libpurple to do this in a protocol-independent way rather than using a prpl action on MSN and setting the nickname field on xmpp and a prpl action on AIM and ... |
| 37 | | * Avatars |
| 38 | | * Retrieving remote avatars, and your current avatar, works |
| 39 | | * You cannot set your own avatar. (Empathy doesn't support this either, so. :-)) |
| 40 | | * Typing notifications |
| 41 | | |
| 42 | | ==== Unimplemented ==== |
| 43 | | |
| 44 | | * Multi-user chats |
| 45 | | * Privacy |
| 46 | | * Everything I've forgotten. |
| 47 | | |
| 48 | | === Telepathy prpl === |
| 49 | | |
| 50 | | * Not started yet. |
| 51 | | |
| 52 | | === Possible further work === |
| 53 | | |
| 54 | | * A plugin to migrate existing accounts in Pidgin to use Telepathy. |
| 55 | | |
| 56 | | == Status == |
| 57 | | |
| 58 | | Grab [http://salami.ox.compsoc.net/~resiak/haze/haze-0.1.1.tar.gz telepathy-haze 0.1.1] ("Release less often, release correctly"). You may also want some [http://salami.ox.compsoc.net/~resiak/haze/profiles/ profiles] to use it with mission-control, although I believe recent Empathys include some telepathy-haze profiles. |
| 59 | | |
| 60 | | == Development == |
| 61 | | |
| 62 | | `telepathy-haze` is kept in a [WikiPedia:Darcs] repository, currently at [http://salami.ox.compsoc.net/~resiak/darcs/telepathy-haze/]. In the nearish future, it will move to [http://projects.collabora.co.uk/darcs/telepathy/] to be alongside most other Telepathy components. (Darcs is the ''de facto'' standard VCS for Telepathy components.) |
| 63 | | |
| 64 | | Haze should work with any released libpurple. If you want to use Empathy or some other libmissioncontrol-based Telepathy UI, you'll need at least [http://sourceforge.net/project/showfiles.php?group_id=190214&package_id=224579&release_id=529338 libmissioncontrol 4.31]. (Older versions choked on .manager files with more than one protocol.) |
| 65 | | |
| 66 | | The Telepathy prpl will be developed in the `im.pidgin.soc.2007.telepathy` branch; right now there's nothing useful in it. |
| | 22 | (The `im.pidgin.soc.2007.telepathy` branch of pidgin.im's monotone repository contains nothing useful.) |
