<?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/"
		>
<channel>
	<title>Comments for Robotic Tendencies</title>
	<atom:link href="http://robot101.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://robot101.net</link>
	<description>The personal blog of Robert McQueen</description>
	<lastBuildDate>Sun, 06 Jun 2010 14:23:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Telepathy Q&amp;A from the Boston GNOME Summit by Cliff Wells</title>
		<link>http://robot101.net/2009/10/14/telepathy-qa/comment-page-1/#comment-42381</link>
		<dc:creator>Cliff Wells</dc:creator>
		<pubDate>Sun, 06 Jun 2010 14:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=114#comment-42381</guid>
		<description>I&#039;m glad to hear OTR is back under consideration.  I will personally never use an IM client that doesn&#039;t support end-to-end encryption.

That being said, I&#039;m not tied to OTR and would gladly consider an alternative. However, according to the Telepathy FAQ, the plan is to implement XEP-0246, but that proposed standard has been deferred and not recommended:

http://xmpp.org/extensions/xep-0246.html

What *is* the current plan for end-to-end encryption?</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to hear OTR is back under consideration.  I will personally never use an IM client that doesn&#8217;t support end-to-end encryption.</p>
<p>That being said, I&#8217;m not tied to OTR and would gladly consider an alternative. However, according to the Telepathy FAQ, the plan is to implement XEP-0246, but that proposed standard has been deferred and not recommended:</p>
<p><a href="http://xmpp.org/extensions/xep-0246.html" rel="nofollow">http://xmpp.org/extensions/xep-0246.html</a></p>
<p>What *is* the current plan for end-to-end encryption?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VP8 rumblings by Robert McQueen</title>
		<link>http://robot101.net/2010/05/21/vp8-rumblings/comment-page-1/#comment-42330</link>
		<dc:creator>Robert McQueen</dc:creator>
		<pubDate>Mon, 24 May 2010 00:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=123#comment-42330</guid>
		<description>Sean: Sure, H264 can and will live on in many of the places it&#039;s deployed, and I know Google provides no indemnification, but it&#039;s interesting for more than the reasons you say. If Google start flipping the appropriate switches, there will be a few companies who will end up in the position to choose between allowing their end-users to access Google&#039;s VP8 only content, or a video codec IPR licensing revenue. Other people&#039;s patents might very well be applicable to VP8, and people can (and very most likely will) license those via the MPEG-LA or similar, but if any of those people want to license Google&#039;s IPR on the codec standard themselves, they are obliged not to initiate any litigation or they lose their right to Google&#039;s IPR and are at risk of an incoming lawsuit from Google. So for people who want to produce or consume VP8 content, it turns the video codec IPR into something you can pay for, but not make any money from, which adjusts the game slightly and means there&#039;s likely to be more industry backlash and pooling of resources against patent trolls, like the OIN.</description>
		<content:encoded><![CDATA[<p>Sean: Sure, H264 can and will live on in many of the places it&#8217;s deployed, and I know Google provides no indemnification, but it&#8217;s interesting for more than the reasons you say. If Google start flipping the appropriate switches, there will be a few companies who will end up in the position to choose between allowing their end-users to access Google&#8217;s VP8 only content, or a video codec IPR licensing revenue. Other people&#8217;s patents might very well be applicable to VP8, and people can (and very most likely will) license those via the MPEG-LA or similar, but if any of those people want to license Google&#8217;s IPR on the codec standard themselves, they are obliged not to initiate any litigation or they lose their right to Google&#8217;s IPR and are at risk of an incoming lawsuit from Google. So for people who want to produce or consume VP8 content, it turns the video codec IPR into something you can pay for, but not make any money from, which adjusts the game slightly and means there&#8217;s likely to be more industry backlash and pooling of resources against patent trolls, like the OIN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VP8 rumblings by ginger&#39;s thoughts &#187; VP8/WebM: Adobe is the key to open video on the Web</title>
		<link>http://robot101.net/2010/05/21/vp8-rumblings/comment-page-1/#comment-42323</link>
		<dc:creator>ginger&#39;s thoughts &#187; VP8/WebM: Adobe is the key to open video on the Web</dc:creator>
		<pubDate>Sat, 22 May 2010 13:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=123#comment-42323</guid>
		<description>[...] I believe the threat is really minimal. You should also read these thoughts of a Gnome developer, these of a Debian developer and the emails on the Theora mailing list.    11 [...]</description>
		<content:encoded><![CDATA[<p>[...] I believe the threat is really minimal. You should also read these thoughts of a Gnome developer, these of a Debian developer and the emails on the Theora mailing list.    11 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VP8 rumblings by Sean</title>
		<link>http://robot101.net/2010/05/21/vp8-rumblings/comment-page-1/#comment-42320</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Fri, 21 May 2010 20:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=123#comment-42320</guid>
		<description>Given that the MPEG-LA makes a ton of money from contexts that VP8 is totally worthless for and has zero cash flow for the contexts VP8 is targeted at, I doubt that the MPEG-LA cares all that much.  I&#039;m sure they plan on attacking VP8 any way they can just out of principle and opportunity, but in no way is Google going to harm their actual business model.  VP8 is only targeted at low to mid quality Internet video streaming, where as .h264 and friends are used for very high quality streaming as well as traditional media and archiving.

Also, keep in mind that Google&#039;s license does not guarantee zero royalties in the event that VP8 actually is found to be infringing on some patents.  Google gives you a grant to use the licenses it owns; it is not legally capable of granting you a license to other parties&#039; patents.  Google does not indemnify WebM license recipients, so a user of VP8 could still be sued by MPEG-LA (assuming that they actually do have patents that cover VP8, of course).  It&#039;s probably safe for a hobbyist to assume that Google did its research here, but a corporation might want to wait a while and see if the MPEG-LA has any teeth backing up its bark or not first.

Honestly, though, the only reason VP8 stands to be interesting at all is that it may bring on a few more companies to the Open Internet Video Club that Theora couldn&#039;t pull in, purely for political and marketing reasons.  Perhaps it&#039;s a slightly better codec than Theora, but in the end it doesn&#039;t really do anything for the Internet that Theora didn&#039;t already do.  It&#039;s just got Google&#039;s money and reputation backing it up.  The problem where several major players said &quot;we&#039;re using .h264 for our  tag support, and that&#039;s it&quot; isn&#039;t magically going away just because of VP8/WebM.</description>
		<content:encoded><![CDATA[<p>Given that the MPEG-LA makes a ton of money from contexts that VP8 is totally worthless for and has zero cash flow for the contexts VP8 is targeted at, I doubt that the MPEG-LA cares all that much.  I&#8217;m sure they plan on attacking VP8 any way they can just out of principle and opportunity, but in no way is Google going to harm their actual business model.  VP8 is only targeted at low to mid quality Internet video streaming, where as .h264 and friends are used for very high quality streaming as well as traditional media and archiving.</p>
<p>Also, keep in mind that Google&#8217;s license does not guarantee zero royalties in the event that VP8 actually is found to be infringing on some patents.  Google gives you a grant to use the licenses it owns; it is not legally capable of granting you a license to other parties&#8217; patents.  Google does not indemnify WebM license recipients, so a user of VP8 could still be sued by MPEG-LA (assuming that they actually do have patents that cover VP8, of course).  It&#8217;s probably safe for a hobbyist to assume that Google did its research here, but a corporation might want to wait a while and see if the MPEG-LA has any teeth backing up its bark or not first.</p>
<p>Honestly, though, the only reason VP8 stands to be interesting at all is that it may bring on a few more companies to the Open Internet Video Club that Theora couldn&#8217;t pull in, purely for political and marketing reasons.  Perhaps it&#8217;s a slightly better codec than Theora, but in the end it doesn&#8217;t really do anything for the Internet that Theora didn&#8217;t already do.  It&#8217;s just got Google&#8217;s money and reputation backing it up.  The problem where several major players said &#8220;we&#8217;re using .h264 for our  tag support, and that&#8217;s it&#8221; isn&#8217;t magically going away just because of VP8/WebM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Telepathy Q&amp;A from the Boston GNOME Summit by robotfan101</title>
		<link>http://robot101.net/2009/10/14/telepathy-qa/comment-page-1/#comment-42277</link>
		<dc:creator>robotfan101</dc:creator>
		<pubDate>Wed, 14 Oct 2009 08:40:06 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=114#comment-42277</guid>
		<description>Telepathy is teh awesome. I want yr babys.</description>
		<content:encoded><![CDATA[<p>Telepathy is teh awesome. I want yr babys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Telepathy Q&amp;A from the Boston GNOME Summit by nelson</title>
		<link>http://robot101.net/2009/10/14/telepathy-qa/comment-page-1/#comment-42276</link>
		<dc:creator>nelson</dc:creator>
		<pubDate>Wed, 14 Oct 2009 08:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=114#comment-42276</guid>
		<description>It would be cool to build an online board game framework on top of telepathy based on the design of GtkBoard, see http://gtkboard.sourceforge.net/indexold.html</description>
		<content:encoded><![CDATA[<p>It would be cool to build an online board game framework on top of telepathy based on the design of GtkBoard, see <a href="http://gtkboard.sourceforge.net/indexold.html" rel="nofollow">http://gtkboard.sourceforge.net/indexold.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Today&#8217;s the day by foo</title>
		<link>http://robot101.net/2009/08/27/todays-the-day/comment-page-1/#comment-42258</link>
		<dc:creator>foo</dc:creator>
		<pubDate>Thu, 27 Aug 2009 16:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/2009/08/27/todays-the-day/#comment-42258</guid>
		<description>Ewwwww, flash. And why not Debian on your mobile device??</description>
		<content:encoded><![CDATA[<p>Ewwwww, flash. And why not Debian on your mobile device??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Top acts by Toby</title>
		<link>http://robot101.net/2009/03/13/top-acts/comment-page-1/#comment-42221</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Thu, 02 Apr 2009 16:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=104#comment-42221</guid>
		<description>On the &#039;top&#039; theme, there is also mytop (and innotop).

http://www.xaprb.com/innotop/
http://jeremy.zawodny.com/mysql/mytop/</description>
		<content:encoded><![CDATA[<p>On the &#8216;top&#8217; theme, there is also mytop (and innotop).</p>
<p><a href="http://www.xaprb.com/innotop/" rel="nofollow">http://www.xaprb.com/innotop/</a><br />
<a href="http://jeremy.zawodny.com/mysql/mytop/" rel="nofollow">http://jeremy.zawodny.com/mysql/mytop/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Top acts by Alban</title>
		<link>http://robot101.net/2009/03/13/top-acts/comment-page-1/#comment-42217</link>
		<dc:creator>Alban</dc:creator>
		<pubDate>Fri, 27 Mar 2009 11:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=104#comment-42217</guid>
		<description>Also mtop, for mysql</description>
		<content:encoded><![CDATA[<p>Also mtop, for mysql</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on This is a local mail for local people, we&#8217;ll have no trouble here! by Colin Thomson</title>
		<link>http://robot101.net/2009/03/06/local-mail/comment-page-1/#comment-42210</link>
		<dc:creator>Colin Thomson</dc:creator>
		<pubDate>Fri, 20 Mar 2009 22:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://robot101.net/?p=86#comment-42210</guid>
		<description>I&#039;m a bit late here, and I know your problem is solved, but do you need local mail to run through dspam? Postfix can have different local and virtual delivery systems. Why not use the mailbox command for local mail, delivering directly to dovecot, and specify virtual_transport = lmtp:unix:/tmp/dspam.sock to send virtual users mail through dspam?</description>
		<content:encoded><![CDATA[<p>I&#8217;m a bit late here, and I know your problem is solved, but do you need local mail to run through dspam? Postfix can have different local and virtual delivery systems. Why not use the mailbox command for local mail, delivering directly to dovecot, and specify virtual_transport = lmtp:unix:/tmp/dspam.sock to send virtual users mail through dspam?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
