<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Edd Dumbill's Weblog: 'podcasts' articles</title>
  <link href="http://times.usefulinc.com/tagpodcastsatom" rel="self"/>
  <link href="http://times.usefulinc.com/tagpodcasts" rel="alternate"/>
  <id>http://times.usefulinc.com/</id>
  <updated>2006-09-06T14:11:58Z</updated>
  <author>
    <name>Edd Dumbill</name>
    <email>edd-web@usefulinc.com</email>
  </author>
  <entry>
    <title>New home for Monopod</title>
    <link href="http://times.usefulinc.com/2006/09/06-monopod" rel="alternate"/>
    <id>http://times.usefulinc.com/public/read/860</id>
    <updated>2006-09-06T14:11:58Z</updated>
    <published>2006-09-06T14:07:53Z</published>
    <summary>Nickolay Shmyrev has taken over as the new maintainer of Monopod, my simple podcast client for the GNOME desktop.</summary>
    <category term="podcasts"/>
    <category term="mono"/>
    <content type="html">
&lt;p&gt;I'm pleased to report that Nickolay Shmyrev has taken over as the new maintainer of Monopod, my simple podcast client for the GNOME desktop.&lt;/p&gt;&lt;p&gt;Monopod now has a new &lt;a href="http://monopod.berlios.de/"&gt;home page&lt;/a&gt;, and a publicly available &lt;a href="http://developer.berlios.de/projects/monopod/"&gt;Subversion repository&lt;/a&gt;. My thanks to Nickolay for taking this on.&lt;/p&gt;&lt;p&gt;A &lt;a href="http://gnomefiles.org/app.php/Monopod"&gt;new release&lt;/a&gt; is now available, which makes Monopod build with the latest ipod-sharp code. If you're in the market for a drop-dead simple podcast client, Monopod's still a great choice.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2006/09/06-monopod#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;    </content>
  </entry>
  <entry>
    <title>New Monopod release</title>
    <link href="http://times.usefulinc.com/2005/07/31-monopod" rel="alternate"/>
    <id>http://times.usefulinc.com/public/read/803</id>
    <updated>2005-07-31T18:31:25Z</updated>
    <published>2005-07-31T18:31:25Z</published>
    <summary>A long-await release of Monopod, with bleeding-edge iPod support</summary>
    <category term="podcasts"/>
    <content type="html">
&lt;div&gt;
&lt;p&gt;I've just released &lt;a href="http://downloads.usefulinc.com/monopod/monopod-0.4.tar.gz"&gt;monopod 0.4&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Monopod is &lt;a href="http://usefulinc.com/edd/blog/contents/2005/06/17-monopod/read"&gt;a simple podcast client&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Version 0.4 fixes a couple of annoying bugs (doesn't reload all
podcasts each time, gets over omission of type in KCRW feeds), and includes
a few new bits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the first translation (Dutch, from &lt;a href="http://uwstopia.nl/"&gt;Wouter Bolsterlee&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;recent.m3u&lt;/code&gt; playlist with the 50 most recent downloads&lt;/li&gt;
&lt;li&gt;bundles entagged-sharp for reading MP3 metadata&lt;/li&gt;
&lt;li&gt;iPod support&lt;/li&gt;

&lt;/ul&gt;
&lt;p&gt;However, don't get too excited yet about the iPod support.
First up, you'll need ipod-sharp installed from the Mono
Subversion repository, and libipoddevice from GNOME CVS.
If you've got that far, then you'll realise that means
latest-greatest DBUS and HAL--in other words, a bleeding-edge
GNOME setup.&lt;/p&gt;
&lt;p&gt;Add to that, the iPod support may or may not work properly.
It's definitely going to be a "GNOME 2.12" level
feature. But I thought I'd land it in the release anyway,
so more work will get done on it in the future.&lt;/p&gt;
&lt;p&gt;Of course, Monopod will build fine without iPod support.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;a href="http://times.usefulinc.com/2005/07/31-monopod#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;    </content>
  </entry>
  <entry>
    <title>A first look at iTunes RSS extensions</title>
    <link href="http://times.usefulinc.com/2005/06/28-rss-apple-itunes" rel="alternate"/>
    <id>http://times.usefulinc.com/public/read/799</id>
    <updated>2005-06-28T16:56:40Z</updated>
    <published>2005-06-28T16:56:40Z</published>
    <summary>A review of the extensions to RSS 2.0 Apple have created to support podcasts in the iTunes store.</summary>
    <category term="podcasts"/>
    <content type="html">
&lt;div&gt;
&lt;p&gt;Apple have &lt;a href="http://www.apple.com/pr/library/2005/jun/28podcast.html"&gt;released iTunes
4.9&lt;/a&gt; with
support for downloading podcasts.  At the same time, they've released
a set of extensions for RSS that affects how podcasts will show up in
the iTunes Music Store.&lt;/p&gt;
&lt;p&gt;The specification can be &lt;a href="http://phobos.apple.com/static/podcast_specifications.pdf"&gt;downloaded as a
PDF&lt;/a&gt; from
Apple's site.  (It annoys me how Apple don't quite get this web thing,
despite being cool in other respects.)&lt;/p&gt;
&lt;p&gt;Here's a quick review of the elements they've specified.&lt;/p&gt;
&lt;p&gt;First up, the namespace,
&lt;i&gt;http://www.itunes.com/DTDs/Podcast-1.0.dtd&lt;/i&gt;.  Apparently DTD as
a namespace, containing a version number in the name.  Almost always a
bad idea.  Versioning and namespaces are a complex mix, and limiting
future flexibility by changing the namespace with each revision can be
a bad idea.  Try resolving that URI, and you get redirected to an HTML
page.  &lt;b&gt;Verdict: poor&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;Let's look at something helpful now. The &lt;i&gt;itunes:duration&lt;/i&gt;
element is useful, carrying some much-needed extra metadata about
audio content. &lt;b&gt;Verdict: good&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;Next up, there's a bunch of replicated Dublin Core type metadata, all
in the iTunes namespace: &lt;i&gt;owner, name, email, author, keywords&lt;/i&gt;.  It would
have been nice if existing conventions for &lt;i&gt;dc:publisher&lt;/i&gt;,
&lt;i&gt;dc:creator&lt;/i&gt; etc. could have been re-used. That way RSS feeds
won't get cluttered with multiple redundant elements.  Nevertheless, I
can see why iTunes might want all this stuff completely
disambiguated.  They don't imagine finding RSS in the wild and adding
it to the iTunes store, instead they expect people to create RSS with
the express purpose of lodging it with iTunes.  &lt;b&gt;Verdict: so-so&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;There's an  &lt;i&gt;itunes:image&lt;/i&gt; element, for specifying imagery for
the iTunes store.  Reuse is less likely in this case, so a dedicated
element makes total sense.  &lt;b&gt;Verdict: good&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;A selection of elements cover textual description.  We all know about
RSS's &lt;em&gt;description&lt;/em&gt;, but iTunes adds &lt;em&gt;itunes:summary&lt;/em&gt; and
&lt;em&gt;itunes:subtitle&lt;/em&gt;.  Both of these elements are mandated to be plain
text.  In most cases, it looks like &lt;em&gt;summary&lt;/em&gt; should be the same as
&lt;em&gt;description&lt;/em&gt;.  The egregious practice of including escaped HTML in
&lt;em&gt;description&lt;/em&gt;--which was meant to be a plaintext field--has meant this
situation is just about unavoidable.  I do worry that with title,
description, summary and subtitle this is all getting rather too
complex.  &lt;b&gt;Verdict: okay&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;Categorisation within the iTunes store is handled by the
&lt;em&gt;itunes:category&lt;/em&gt; element.  You have to see this markup to believe it:&lt;/p&gt;
&lt;p&gt;&lt;pre&gt; &amp;lt;itunes:category text="Technology"&gt;
   &amp;lt;itunes:category text="Gadgets" /&gt;
 &amp;lt;/itunes:category&gt;
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Add to that a prose restriction that categories can only be nested to
two levels and I'm left scratching my head. It also stands out as just
about the only attribute-carried text content within RSS. &lt;b&gt;Verdict:
nuts&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;The remaining elements are used to control content restrictions within
iTunes.  The &lt;em&gt;itunes:explicit&lt;/em&gt; element is meant to be included if your
content is "explicit".  Okay... And &lt;em&gt;itunes:block&lt;/em&gt; can be used to
block a podcast from appearing in the iTunes store.  These elements
seem vague, underspecified and certainly open to abuse. &lt;b&gt;Verdict:
poor.&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;Some miscellaneous observations.  iTunes wants RSS feeds in UTF-8.
&lt;b&gt;Verdict: good&lt;/b&gt;.  Aside from &lt;em&gt;itunes:summary&lt;/em&gt;, "all fields will
be truncated to 255 characters". &lt;b&gt;Verdict: daft&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;I'd like to provide more detail, but on clicking the "Learn more" link
on Apple's &lt;a href="http://www.apple.com/podcasting"&gt;podcasting page&lt;/a&gt; results
in a blank page on my Firefox, with an error "itmss is not a
registered protocol".  &lt;b&gt;Verdict: gob-smackingly ignorant&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;What could have been a useful and reusable addition to the world of
RSS is really rendered only fit for the single use of adding content
into Apple's own iTunes store.  Apple prove they know how to be cool,
but they've got no idea about making friends on the web.&lt;/p&gt;
&lt;p&gt;From the point of view of XML and the web, iTunes RSS extensions are
somewhat disappointing.  From a professional point of view, I'd say
this looks rather embarrassing: Apple clearly don't have enough
people who really understand XML.&lt;/p&gt;
&lt;p&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.reallysimplesyndication.com/2005/06/28#a682"&gt;Dave Winer&lt;/a&gt;
also has some criticism for the iTunes extensions. "Come on Apple, we can do better."
&lt;/li&gt;
&lt;/ul&gt;&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;a href="http://times.usefulinc.com/2005/06/28-rss-apple-itunes#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;    </content>
  </entry>
  <entry>
    <title>Fresh Monopod</title>
    <link href="http://times.usefulinc.com/2005/06/21-monopod" rel="alternate"/>
    <id>http://times.usefulinc.com/public/read/797</id>
    <updated>2005-06-21T23:18:26Z</updated>
    <published>2005-06-21T23:18:26Z</published>
    <summary>Version 0.3 of Monopod is out!</summary>
    <category term="podcasts"/>
    <content type="html">
&lt;div&gt;
&lt;p&gt;&lt;img src="http://usefulinc.com/edd/blog/contents/2005/06/monopod.png" style="float: right; margin: 8px; height: 32px; width: 32px;"
alt="Monopod logo" /&gt; I've just released &lt;a href="http://downloads.usefulinc.com/monopod/monopod-0.3.tar.gz"&gt;monopod 0.3&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Monopod is &lt;a href="http://usefulinc.com/edd/blog/contents/2005/06/17-monopod/read"&gt;a simple podcast client&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Version 0.3 fixes a few bugs and actually makes the program useful for more than
one channel.&lt;/p&gt;
&lt;p&gt;Here are the new features:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GNOME Proxy support&lt;/li&gt;
&lt;li&gt;I18N-enabled sources&lt;/li&gt;
&lt;li&gt;"Show Podcasts" menu item&lt;/li&gt;
&lt;li&gt;GNOME Applications menu entry&lt;/li&gt;
&lt;li&gt;A few more default channels, from KCRW&lt;/li&gt;

&lt;/ul&gt;
&lt;p&gt;&lt;a href="http://www.snorp.net/log/?p=55"&gt;iPod support&lt;/a&gt; cannot be too far away.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;a href="http://times.usefulinc.com/2005/06/21-monopod#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;    </content>
  </entry>
</feed>
