Mercurial > pidgin.yaz
comparison libpurple/protocols/myspace/zap.c @ 27109:fdc0035bea5a
Change the way we parse messages on MySpace a little bit. This
fixes #8846: people using web myspaceIM can't respond to pidgin myspaceIM
For some reason IMs send using the myspace web site are sent so that
they won't become offline messages if the other person is offline.
I'm not really sure why that decision was made.
So now we treat messages with bm 1 the same as messages with bm 121. This means
we have to combine the function that parses out typing notification with
the function that parses IMs. And we check for typing notifications by
looking for %typing%. Which means if someone sends the IM "%typing%" with
no markup then we'll interpret it as a typing notification. And there's
nothing we can do to differentiate between the two. I asked.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Thu, 04 Jun 2009 05:19:49 +0000 |
parents | e22bc87b758b |
children | 5fbcfcbd6551 |
comparison
equal
deleted
inserted
replaced
27108:53294b47a4a6 | 27109:fdc0035bea5a |
---|---|
107 g_return_val_if_fail(username != NULL, FALSE); | 107 g_return_val_if_fail(username != NULL, FALSE); |
108 | 108 |
109 /* Construct and send the actual zap command. */ | 109 /* Construct and send the actual zap command. */ |
110 zap_string = g_strdup_printf("!!!ZAP_SEND!!!=RTE_BTN_ZAPS_%d", code); | 110 zap_string = g_strdup_printf("!!!ZAP_SEND!!!=RTE_BTN_ZAPS_%d", code); |
111 | 111 |
112 if (!msim_send_bm(session, username, zap_string, MSIM_BM_ACTION)) { | 112 if (!msim_send_bm(session, username, zap_string, MSIM_BM_INSTANT_ACTION_OR_IM)) { |
113 purple_debug_info("msim_send_zap", | 113 purple_debug_info("msim_send_zap", |
114 "msim_send_bm failed: zapping %s with %s\n", | 114 "msim_send_bm failed: zapping %s with %s\n", |
115 username, zap_string); | 115 username, zap_string); |
116 rc = FALSE; | 116 rc = FALSE; |
117 } else { | 117 } else { |