<?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 on: Apple Blocks Podcaster Ad-hoc Distribution</title> <atom:link href="http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/feed/" rel="self" type="application/rss+xml" /><link>http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/</link> <description>Everyone can understand technology; sometimes it just takes a little translating.</description> <lastBuildDate>Tue, 14 Feb 2012 14:00:10 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: reidme</title><link>http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/#comment-39867</link> <dc:creator>reidme</dc:creator> <pubDate>Wed, 24 Sep 2008 15:12:12 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/?p=14152#comment-39867</guid> <description>This seems incredibly heavy handed.  No way Apple is really worried about &quot;confusing&quot; the customer with duplicate alternatives.  One look at all the duplication currently in the app store discredits that claim.  They&#039;re worried about competition and the possibility that their iPodiTunesiTunesStore stranglehold might get compromised.  They don&#039;t want the precedent set for getting your content any other way. Preventing ad hoc distribution practically proves this.</description> <content:encoded><![CDATA[<p>This seems incredibly heavy handed.  No way Apple is really worried about &#8220;confusing&#8221; the customer with duplicate alternatives.  One look at all the duplication currently in the app store discredits that claim.  They&#8217;re worried about competition and the possibility that their iPodiTunesiTunesStore stranglehold might get compromised.  They don&#8217;t want the precedent set for getting your content any other way. Preventing ad hoc distribution practically proves this.</p> ]]></content:encoded> </item> <item><title>By: chrisspera</title><link>http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/#comment-56189</link> <dc:creator>chrisspera</dc:creator> <pubDate>Wed, 24 Sep 2008 15:00:05 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/?p=14152#comment-56189</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Podcaster Ad-hoc Distribution Blocked - The ultimate b-slap?? http://ping.fm/gGyyO&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span
class="topsy_trackback_comment"><span
class="topsy_twitter_username"><span
class="topsy_trackback_content">Podcaster Ad-hoc Distribution Blocked &#8211; The ultimate b-slap?? <a
href="http://ping.fm/gGyyO" rel="nofollow">http://ping.fm/gGyyO</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Christopher Gavula</title><link>http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/#comment-39866</link> <dc:creator>Christopher Gavula</dc:creator> <pubDate>Wed, 24 Sep 2008 14:42:51 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/?p=14152#comment-39866</guid> <description>I should add (without knowing where Alex posted his comments that were later removed) that Apple has always had a policy of removing comments at will from their forums.  Apple own that service and their forums are NOT a public forum in that they clearly reserve the right to do what they will when you sign up to use their forums.  I can understand that.  But this new policy prohibits developers from speaking on ANY forum about their rejection (or, more specifically, anything in their acceptance/rejection letter).  That I have a problem with.</description> <content:encoded><![CDATA[<p>I should add (without knowing where Alex posted his comments that were later removed) that Apple has always had a policy of removing comments at will from their forums.  Apple own that service and their forums are NOT a public forum in that they clearly reserve the right to do what they will when you sign up to use their forums.  I can understand that.  But this new policy prohibits developers from speaking on ANY forum about their rejection (or, more specifically, anything in their acceptance/rejection letter).  That I have a problem with.</p> ]]></content:encoded> </item> <item><title>By: Christopher Gavula</title><link>http://www.geardiary.com/2008/09/24/apple-blocks-ad-hoc/#comment-39865</link> <dc:creator>Christopher Gavula</dc:creator> <pubDate>Wed, 24 Sep 2008 14:38:15 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/?p=14152#comment-39865</guid> <description>Apple did something else disturbing today.  There&#039;s a report on macnn.com that Apple has now modified the developer NDA to include not talking about a rejected app.
One thing about the Apple process is that people have been free to publicly complain about Apple practices.  Now it seems Apple wants to stop that too.  Definitely not a good thing for developers or consumers and I don&#039;t see how it&#039;s really enforceable except by prohibiting a developer from EVER developing for the platform and distributing via the AppStore, but then, if a developer got rejected in this way he/she probably doesn&#039;t care about that!</description> <content:encoded><![CDATA[<p>Apple did something else disturbing today.  There&#8217;s a report on macnn.com that Apple has now modified the developer NDA to include not talking about a rejected app.</p><p>One thing about the Apple process is that people have been free to publicly complain about Apple practices.  Now it seems Apple wants to stop that too.  Definitely not a good thing for developers or consumers and I don&#8217;t see how it&#8217;s really enforceable except by prohibiting a developer from EVER developing for the platform and distributing via the AppStore, but then, if a developer got rejected in this way he/she probably doesn&#8217;t care about that!</p> ]]></content:encoded> </item> </channel> </rss>
