<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: PremiumCast &#8211; Pay to Listen Podcasting</title>
	<atom:link href="http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/</link>
	<description>Digital Podcast focuses on using new and social media to build real businesses.  We help publishers build new media businesses that use best practices to market content, build audience and monetize the results.  Give us a call at 562-824-5193.</description>
	<lastBuildDate>Wed, 11 Nov 2009 20:29:23 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Josh Anderson</title>
		<link>http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/comment-page-1/#comment-58303</link>
		<dc:creator>Josh Anderson</dc:creator>
		<pubDate>Mon, 24 Sep 2007 20:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/#comment-58303</guid>
		<description>Hi Alex,

We went ahead and changed the format of the confirmation link so the security issue you brought up is now resolved and no longer exists :-)

Thanks again for the review of Premiumcast.com 

Additionally there have been some new updates, simplifications, and a great new private feed security feature as well but I will let Paul update you on that.

We are very excited to have our technology now opened to the public.</description>
		<content:encoded><![CDATA[<p>Hi Alex,</p>
<p>We went ahead and changed the format of the confirmation link so the security issue you brought up is now resolved and no longer exists <img src='http://www.digitalpodcast.com/podcastnews/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Thanks again for the review of Premiumcast.com </p>
<p>Additionally there have been some new updates, simplifications, and a great new private feed security feature as well but I will let Paul update you on that.</p>
<p>We are very excited to have our technology now opened to the public.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/comment-page-1/#comment-58202</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Fri, 21 Sep 2007 14:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/#comment-58202</guid>
		<description>Paul,

Glad to hear you will add that to your list.  Looks like you have a good and useful service going there.  Good luck with it.

Alex</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Glad to hear you will add that to your list.  Looks like you have a good and useful service going there.  Good luck with it.</p>
<p>Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Colligan</title>
		<link>http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/comment-page-1/#comment-58200</link>
		<dc:creator>Paul Colligan</dc:creator>
		<pubDate>Fri, 21 Sep 2007 14:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalpodcast.com/podcastnews/2007/09/20/premiumcast-pay-to-listen-podcasting/#comment-58200</guid>
		<description>Thanks for reporting on this - we appreciate it muchly.  In terms of the security issue you brought up, it has been added to our to do list.

Paul</description>
		<content:encoded><![CDATA[<p>Thanks for reporting on this &#8211; we appreciate it muchly.  In terms of the security issue you brought up, it has been added to our to do list.</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
