<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: LiveJournal Goes XMPP-Jabber</title>
	<atom:link href="http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/</link>
	<description>Trusted Insights and Conversations on the Next Wave of Technology</description>
	<lastBuildDate>Thu, 26 Nov 2009 06:47:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BoardReader</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56443</link>
		<dc:creator>BoardReader</dc:creator>
		<pubDate>Wed, 07 Feb 2007 14:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56443</guid>
		<description>&lt;p&gt;It&#039;s great! It&#039;s good as for Jabber as for LiveJournal community!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s great! It&#8217;s good as for Jabber as for LiveJournal community!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: wildfire</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56438</link>
		<dc:creator>wildfire</dc:creator>
		<pubDate>Sat, 09 Sep 2006 13:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56438</guid>
		<description>&lt;p&gt;Brad did a nice job. Djabberd supports more concurrent users than any xmpp server.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Brad did a nice job. Djabberd supports more concurrent users than any xmpp server.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolas Coukouma</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56435</link>
		<dc:creator>Nikolas Coukouma</dc:creator>
		<pubDate>Wed, 12 Jul 2006 12:18:51 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56435</guid>
		<description>&lt;p&gt;Google Talk federation is automatic, since it&#039;s just another XMPP/Jabber server. Gizmo uses XMPP for chat and presence, so that works automatically too. For voice, Gizmo uses SIP, which is separate. LiveJournal allows you to post recordings to your journal (voice post); you can already call ljvoicepost on Gizmo (sip:ljvoicepost@proxy01.sipphone.com), or use a &lt;a HREF=&quot;http://www.livejournal.com/voicepost/numbers.bml&quot; rel=&quot;nofollow&quot;&gt;regular phone number&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Integrating SIP/SIMPLE with Jabber is &lt;a HREF=&quot;http://www.ietf.org/internet-drafts/draft-saintandre-xmpp-simple-07.txt&quot; rel=&quot;nofollow&quot;&gt;in a draft state&lt;/a&gt; and Google&#039;s &lt;a HREF=&quot;http://www.jabber.org/jeps/jep-0166.html&quot; rel=&quot;nofollow&quot;&gt;Jingle&lt;/a&gt; spec for intra-Jabber VoiP is still very young. And, actually, Jingle will require nothing from the server (DJabberd for livejournal.com); so whenever clients support it, it should just work. AFAIK, the official Google Talk client is the only released Jabber client that actually supports it, though.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Google Talk federation is automatic, since it&#8217;s just another XMPP/Jabber server. Gizmo uses XMPP for chat and presence, so that works automatically too. For voice, Gizmo uses SIP, which is separate. LiveJournal allows you to post recordings to your journal (voice post); you can already call ljvoicepost on Gizmo (sip:ljvoicepost@proxy01.sipphone.com), or use a <a HREF="http://www.livejournal.com/voicepost/numbers.bml" rel="nofollow">regular phone number</a>.</p>

<p>Integrating SIP/SIMPLE with Jabber is <a HREF="http://www.ietf.org/internet-drafts/draft-saintandre-xmpp-simple-07.txt" rel="nofollow">in a draft state</a> and Google&#8217;s <a HREF="http://www.jabber.org/jeps/jep-0166.html" rel="nofollow">Jingle</a> spec for intra-Jabber VoiP is still very young. And, actually, Jingle will require nothing from the server (DJabberd for livejournal.com); so whenever clients support it, it should just work. AFAIK, the official Google Talk client is the only released Jabber client that actually supports it, though.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56433</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Sun, 09 Jul 2006 05:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56433</guid>
		<description>&lt;p&gt;Jabber&#039;s XMPP is the IETF standard for IM and Presence.  Google is using XMPP.  HP, Oracle, Sun, and Apple are major users.&lt;/p&gt;

&lt;p&gt;Here&#039;s an excerpt from a recent Jabber press release:&lt;/p&gt;

&lt;p&gt;&quot;With approval of XMPP by the IETF in 2004, the JSF (Jabber Software Foundation) continues to develop XMPP extensions that meet the needs of its many stakeholders: open-source and commercial developers (including Apple, HP, Oracle, and Sun), organizations large and small (including the U.S. defense establishment and most Wall Street investment banks), Internet and mobile service providers (including Google, NTT, and Orange), and over 25 million end users worldwide.&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Jabber&#8217;s XMPP is the IETF standard for IM and Presence.  Google is using XMPP.  HP, Oracle, Sun, and Apple are major users.</p>

<p>Here&#8217;s an excerpt from a recent Jabber press release:</p>

<p>&#8220;With approval of XMPP by the IETF in 2004, the JSF (Jabber Software Foundation) continues to develop XMPP extensions that meet the needs of its many stakeholders: open-source and commercial developers (including Apple, HP, Oracle, and Sun), organizations large and small (including the U.S. defense establishment and most Wall Street investment banks), Internet and mobile service providers (including Google, NTT, and Orange), and over 25 million end users worldwide.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lj</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56431</link>
		<dc:creator>lj</dc:creator>
		<pubDate>Sun, 09 Jul 2006 03:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56431</guid>
		<description>&lt;p&gt;Lj will be working with Gizmo on voice integration.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Lj will be working with Gizmo on voice integration.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Hirshon</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56414</link>
		<dc:creator>Jonathan Hirshon</dc:creator>
		<pubDate>Sat, 08 Jul 2006 21:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56414</guid>
		<description>&lt;p&gt;Federating IM networks makes perfect sense, using preferred front-ends that specific communities of users prefer using a common lingua franca.  XMPP support in iChat, for example appeals to Mac users, whereas LJ appeals to bloggers, all speaking a common &#039;tongue&#039;, but understandable to others using the same backend.  Think of it as akin to different dialects of English or Mandarin, for example - understandable to anyone who knows the language, but with just enough personality to identify the user as coming from a specific area.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Federating IM networks makes perfect sense, using preferred front-ends that specific communities of users prefer using a common lingua franca.  XMPP support in iChat, for example appeals to Mac users, whereas LJ appeals to bloggers, all speaking a common &#8216;tongue&#8217;, but understandable to others using the same backend.  Think of it as akin to different dialects of English or Mandarin, for example &#8211; understandable to anyone who knows the language, but with just enough personality to identify the user as coming from a specific area.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Borton Jons</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56411</link>
		<dc:creator>Borton Jons</dc:creator>
		<pubDate>Sat, 08 Jul 2006 20:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56411</guid>
		<description>&lt;p&gt;LJ will work with GizmoProject text and presence, but not voice.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>LJ will work with GizmoProject text and presence, but not voice.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: BoardTracker</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56409</link>
		<dc:creator>BoardTracker</dc:creator>
		<pubDate>Sat, 08 Jul 2006 19:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56409</guid>
		<description>&lt;p&gt;We also provide our users with a Jabber IM system and send alerts (for persistant search) to them using that.. since many IM clients these days support multiple protocols including jabber its easy to use many networks, federated or not, but its likely many more jabber networks will continue to spring up now.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We also provide our users with a Jabber IM system and send alerts (for persistant search) to them using that.. since many IM clients these days support multiple protocols including jabber its easy to use many networks, federated or not, but its likely many more jabber networks will continue to spring up now.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Sasha</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56407</link>
		<dc:creator>Sasha</dc:creator>
		<pubDate>Sat, 08 Jul 2006 19:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56407</guid>
		<description>&lt;p&gt;Sorry, the last line should read: &quot;If your buddies already have your IM, why share your IM information with strangers?&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry, the last line should read: &#8220;If your buddies already have your IM, why share your IM information with strangers?&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Sasha</title>
		<link>http://gigaom.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56388</link>
		<dc:creator>Sasha</dc:creator>
		<pubDate>Sat, 08 Jul 2006 19:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2006/07/08/livejournal-goes-xmpp-jabber/#comment-56388</guid>
		<description>&lt;p&gt;This is good news for Jabber/XMPP. I am not sure how much, if any difference it will make for LJ users. Instant messaging on websites is a &lt;a href=&quot;http://snimmer.wordpress.com/2006/06/27/instant-messaging-on-websites/&quot; rel=&quot;nofollow&quot;&gt;challenge&lt;/a&gt; mainly because IM architecture is designed to connect trusted contacts. Websites, including social networks connect various degrees of strangers. You don&#039;t want to share your IM information with strangers. As simple as that.  If my buddies already have your IM, why share your IM information with strangers?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is good news for Jabber/XMPP. I am not sure how much, if any difference it will make for LJ users. Instant messaging on websites is a <a href="http://snimmer.wordpress.com/2006/06/27/instant-messaging-on-websites/" rel="nofollow">challenge</a> mainly because IM architecture is designed to connect trusted contacts. Websites, including social networks connect various degrees of strangers. You don&#8217;t want to share your IM information with strangers. As simple as that.  If my buddies already have your IM, why share your IM information with strangers?</p>]]></content:encoded>
	</item>
</channel>
</rss>
