cpw.darkrain42.xmpp.bosh: 8b60514f: Make my comment parse correctly.

paul at darkrain42.org paul at darkrain42.org
Sun Apr 5 00:45:50 EDT 2009

Revision: 8b60514f2b44295e87ee3587669aec5059556149
Ancestor: 8aa3507dc80559098f9ac283dd24fe367f814bee
Author: paul at darkrain42.org
Date: 2009-04-05T03:25:00
Branch: im.pidgin.cpw.darkrain42.xmpp.bosh
URL: http://d.pidgin.im/viewmtn/revision/info/8b60514f2b44295e87ee3587669aec5059556149

Modified files:


Make my comment parse correctly.

-------------- next part --------------
--- libpurple/protocols/jabber/presence.c	6d78751406f99792f5759a3649295173df146df3
+++ libpurple/protocols/jabber/presence.c	6f122911f2306f7df641955244f849848d1c486d
@@ -278,10 +278,9 @@ xmlnode *jabber_presence_create_js(Jabbe
 	 * This is a huge hack. As far as I can tell, Google Talk's gmail client
 	 * doesn't bother to check the actual features we advertise; they
-	 * just assume that if we advertise a 'voice-v1' ext (ignoring that
-	 * these are to be assigned no semantic value). We need to advertise
-	 * this for the gmail web interface chat client to allow the mail user
-	 * to start a voice chat with us. Boo.
+	 * just assume that if we specify a 'voice-v1' ext (ignoring that
+	 * these are to be assigned no semantic value), we support receiving voice
+	 * calls.
 	if (jabber_audio_enabled(js, NULL /* unused */))
 		xmlnode_set_attrib(c, "ext", "voice-v1");

More information about the Commits mailing list