diff options
| author | George Kiagiadakis <gkiagia@tolabaki.gr> | 2016-06-17 18:14:08 +0300 |
|---|---|---|
| committer | George Kiagiadakis <gkiagia@tolabaki.gr> | 2016-06-17 18:14:08 +0300 |
| commit | 4f1dd6313fc5d9fef67b35254b3e9591737e9fa1 (patch) | |
| tree | afeaa947d9c8317f93868f164ad9e81d20a68b36 /Haze_FAQ.mdwn | |
| parent | 4e52771a764888aa53febc3d0060e7cfc951bae9 (diff) | |
moin2mdwn: convert page Haze_FAQ
Diffstat (limited to 'Haze_FAQ.mdwn')
| -rw-r--r-- | Haze_FAQ.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Haze_FAQ.mdwn b/Haze_FAQ.mdwn new file mode 100644 index 0000000..684d5dd --- /dev/null +++ b/Haze_FAQ.mdwn @@ -0,0 +1,11 @@ + + +## Can I use pidgin-facebookchat/msn-pecan/(insert third-party prpl here) with Haze? + +Kind of. Currently, you'll need to patch `haze.manager`, and add a `.profile` file for the protocol. (This is vaguely outlined on [[this bug report|https://bugs.freedesktop.org/show_bug.cgi?id=17907]].) + +Non-standard protocols will not be added to `haze.manager`. The `.manager` files are intended just to be a cache of what [[ListProtocols()|http://telepathy.freedesktop.org/spec/org.freedesktop.Telepathy.ConnectionManager.html#org.freedesktop.Telepathy.ConnectionManager.ListProtocols]] would return if the CM was running. Since Haze uses libpurple, which loads plugins at runtime, this cache is basically broken. Sadly, current Telepathy clients depend on the presence of a `.manager` file for a CM, so Haze ships the best it can: the set of protocols shipped as standard with libpurple. This means that you can be reasonably sure that if `haze.manager` says a protocol's available, it'll be available when the CM's running. Adding non-standard protocols would break this. + +Correct clients should react to a missing `.manager` file by firing up the CM and interrogating it. `TpConnectionManager` in [[Telepathy GLib|Telepathy GLib]] now does this correctly. Sadly, Mission Control 4 (as used by Empathy) does this wrong. When Empathy moves to Mission Control 5 (which should be in time for Gnome 2.28) then this will all work and `haze.manager` can be deleted. + +Sorry for any inconvenience caused. |