<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for skippy</title><link>http://disqus.com/people/1a320ac7f6818504df79fe42fc6b84a9/</link><description></description><language>en</language><lastBuildDate>Mon, 07 Sep 2009 10:41:34 -0000</lastBuildDate><item><title>Re: The WordPress Attack, Competition and Blogging Innovation</title><link>http://oneman.disqus.com/the_wordpress_attack_competition_and_blogging_innovation/#comment-16095464</link><description>I'm curious what, specifically, you'd advocate Melody or Habari to do to gain traction in this space.&lt;br&gt;&lt;br&gt;Full disclosure: I'm part of the Habari team.&lt;br&gt;&lt;br&gt;I think Habari takes a pretty decent approach to blogging, and security. The fact of the matter is that security is inversely proportional to convenience. The easier we make things to upgrade, the more opportunity we introduce for exploit. :(&lt;br&gt;&lt;br&gt;If you're in the Columbus, OH area this weekend, swing by the first in-person Habari get-together to share your thoughts with the team!&lt;br&gt;&lt;a href="http://groups.google.com/group/habari-users/browse_thread/thread/b8a841cadcce02dc" rel="nofollow"&gt;http://groups.google.com/group/habari-users/bro...&lt;/a&gt;&lt;br&gt;&lt;a href="http://wiki.habariproject.org/en/Habari_Party_2009" rel="nofollow"&gt;http://wiki.habariproject.org/en/Habari_Party_2009&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skippy</dc:creator><pubDate>Mon, 07 Sep 2009 10:41:34 -0000</pubDate></item><item><title>Re: Syncing Audio and Video in Linux</title><link>http://firstclown.disqus.com/syncing_audio_and_video_in_linux/#comment-2810782</link><description>At this tutorial:&lt;br&gt;&lt;a href="http://rhodesmill.org/brandon/2008/how-to-produce-a-linux-screencast/" rel="nofollow"&gt;http://rhodesmill.org/brandon/2008/how-to-produ...&lt;/a&gt;&lt;br&gt;I learned his secret to 'never let “ffmpeg” anywhere near your audio!'  I experienced this problem first-hand when trying to following the Ubuntu screencast tutorial:&lt;br&gt;&lt;a href="https://wiki.ubuntu.com/ScreencastTeam/RecordingScreencasts" rel="nofollow"&gt;https://wiki.ubuntu.com/ScreencastTeam/Recordin...&lt;/a&gt;&lt;br&gt;&lt;br&gt;Excellent PodCamp Ohio presentation!   Thanks for taking the time to share your experiences.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skippy</dc:creator><pubDate>Mon, 30 Jun 2008 11:05:02 -0000</pubDate></item><item><title>Re: My First Habari Plugin</title><link>http://funwithwordpress.disqus.com/my_first_habari_plugin/#comment-3025110</link><description>Excellent introduction!  We know that the documentation is weak right now.  The API is really starting to settle down, so now that it's less of a moving target documentation will get a greater priority.&lt;br&gt;&lt;br&gt;And of course, you're invited to help us generate that documentation!  Your introduction here demonstrates a terrific understanding of what new plugin authors need to gain proficiency.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skippy</dc:creator><pubDate>Fri, 22 Aug 2008 15:50:28 -0000</pubDate></item><item><title>Re: Is WordPress&amp;#8217; licensing too strict?</title><link>http://cdevroe.disqus.com/is_wordpress8217_licensing_too_strict/#comment-7902652</link><description>glibc is released under the LGPL, which specifically permits derivative works to make use of its functionality without "tainting" the derivative works' licensing.  See: &lt;a href="http://en.wikipedia.org/wiki/GNU_C_Library" rel="nofollow"&gt;http://en.wikipedia.org/wiki/GNU_C_Library&lt;/a&gt;&lt;br&gt;&lt;br&gt;GPL contains the viral licensing stipulation, and WordPress' use of the GPL license means that derivative works that are released are obligated to be licensed with a GPL-compatible license.  Derivative works you make but don't release can be licensed however you want.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skippy</dc:creator><pubDate>Wed, 10 Sep 2008 14:24:48 -0000</pubDate></item></channel></rss>