<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pthatcherg</author><text>My original email had more details:&lt;p&gt;We are pleased to announce that we have launched support for Jingle
XEP-166 and XEP-167 for Google Talk calls to and from Gmail, iGoogle,
and Orkut.  We have also added the same level of support to libjingle
(&lt;a href=&quot;http://code.google.com/p/libjingle&quot; rel=&quot;nofollow&quot;&gt;http://code.google.com/p/libjingle&lt;/a&gt;), which is used by many native
clients.  From this point on, it will be our primary signalling
protocol, and the old protocol will only remain for backwards
compatibility.  We also plan to soon update Google Talk on Android to
speak Jingle, but we do not plan on updating the Google Talk Windows
application.&lt;p&gt;We suggest all clients that interop with Google Talk to switch to
using Jingle rather than the old protocol.  We will remain backwards
compatible with legacy clients by continuing to speak the old protocol
as well.  If you wish to continue working with legacy clients, such as
the Google Talk application for Windows, you may also wish to continue
speaking the old protocol.  But the future is Jingle, and the old
protocol will eventually go away.&lt;p&gt;Finally, we are still working on implementing XEP-176 (ICE-UDP).  In
the meantime, you&apos;ll need to use our draft-06 version of ICE, which is
implemented both in libjingle and in libnice, two open source
libraries.&lt;p&gt;I hope that this will be a support to the Jingle community and futher
our efforts to have open standards for voice and video communication.</text><parent_chain></parent_chain></comment><story><title>Google switches GTalk&apos;s VOIP protocol to Jingle</title><url>http://xmpp.org/2011/06/the-future-is-jingle/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>senko</author><text>The annoucement email itself: &lt;a href=&quot;http://mail.jabber.org/pipermail/jingle/2011-June/001640.html&quot; rel=&quot;nofollow&quot;&gt;http://mail.jabber.org/pipermail/jingle/2011-June/001640.htm...&lt;/a&gt;&lt;p&gt;This is great news. Google has been one of the driving forces behind Jingle, but as they were implementing it far in advance of being standardised, the drafts/standards have since changed. Other implementations have to maintain support for several close but not quite the same dialects. Google updating their software will make interop much easier.&lt;p&gt;I&apos;ve been somewhat critical of Google&apos;s attempts in this direction (&lt;a href=&quot;http://senko.net/en/gmail-videochat-the-good-the-bad-and-the-ugly/&quot; rel=&quot;nofollow&quot;&gt;http://senko.net/en/gmail-videochat-the-good-the-bad-and-the...&lt;/a&gt;), and I&apos;m very glad to see I was wrong :)</text><parent_chain></parent_chain></comment><story><title>Google switches GTalk&apos;s VOIP protocol to Jingle</title><url>http://xmpp.org/2011/06/the-future-is-jingle/</url></story>