<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Podcasts. With Vaseline!</title>
	<link>http://moontan.co.za/4Geeks/2006/07/26/podcasts-with-vaseline/</link>
	<description>4 tech-fights, 4 to 40 minutes, 4 everyone</description>
	<pubDate>Sat, 19 May 2012 03:24:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: lala</title>
		<link>http://moontan.co.za/4Geeks/2006/07/26/podcasts-with-vaseline/#comment-123</link>
		<pubDate>Fri, 22 Sep 2006 06:09:32 +0000</pubDate>
		<guid>http://moontan.co.za/4Geeks/2006/07/26/podcasts-with-vaseline/#comment-123</guid>
					<description>I totally understand your problem. It's rediculous. Not to mention the fact they need a credit card for no reason.</description>
		<content:encoded><![CDATA[<p>I totally understand your problem. It&#8217;s rediculous. Not to mention the fact they need a credit card for no reason.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom</title>
		<link>http://moontan.co.za/4Geeks/2006/07/26/podcasts-with-vaseline/#comment-59</link>
		<pubDate>Wed, 26 Jul 2006 22:51:19 +0000</pubDate>
		<guid>http://moontan.co.za/4Geeks/2006/07/26/podcasts-with-vaseline/#comment-59</guid>
					<description>Thought y'all might find this interesting: I've emailed Tom Merrit (Buzz Out Loud podcast at bol.cnet.com), and he's passed this entry on to iTunes. Here's the response:

Hey Tom,
 
I just exchanged email with our contatc at iTunes for podcasting.  Here's his response:
 
His frustration is understandable. 


An account is required to submit a podcast, and since there isn't an iTunes store in South Africa yet, he can't create an account to submit. It's a case of the needs of the Store getting in the way of what should be a more open process when it comes to podcasting. For us, it's important to know who submitted the podcast, as a backup contact person in case the email info in the feed is missing or incorrect--it's another way to establish a line of contact with the podcast submitter. But it causes frustration in places where there isn't a store.


It's not a publicly documented thing, but one easy alternative is for someone to submit them for him. You could submit the feeds and it would be fine. As long as he's got his contact info in the feed itself, then we'll be able to get in touch with him if there's an issue. If you're not comfortable doing it, you could get the feeds from him, send them to me, and I'll submit them from my personal account.</description>
		<content:encoded><![CDATA[<p>Thought y&#8217;all might find this interesting: I&#8217;ve emailed Tom Merrit (Buzz Out Loud podcast at bol.cnet.com), and he&#8217;s passed this entry on to iTunes. Here&#8217;s the response:</p>
<p>Hey Tom,</p>
<p>I just exchanged email with our contatc at iTunes for podcasting.  Here&#8217;s his response:</p>
<p>His frustration is understandable. </p>
<p>An account is required to submit a podcast, and since there isn&#8217;t an iTunes store in South Africa yet, he can&#8217;t create an account to submit. It&#8217;s a case of the needs of the Store getting in the way of what should be a more open process when it comes to podcasting. For us, it&#8217;s important to know who submitted the podcast, as a backup contact person in case the email info in the feed is missing or incorrect&#8211;it&#8217;s another way to establish a line of contact with the podcast submitter. But it causes frustration in places where there isn&#8217;t a store.</p>
<p>It&#8217;s not a publicly documented thing, but one easy alternative is for someone to submit them for him. You could submit the feeds and it would be fine. As long as he&#8217;s got his contact info in the feed itself, then we&#8217;ll be able to get in touch with him if there&#8217;s an issue. If you&#8217;re not comfortable doing it, you could get the feeds from him, send them to me, and I&#8217;ll submit them from my personal account.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

