<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 

	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" 

	xmlns:content="http://purl.org/rss/1.0/modules/content/"

	xmlns:wfw="http://wellformedweb.org/CommentAPI/">
   <channel>
      <title>Tweetair | Croncast - Life is Show Prep</title>
	  <itunes:author>Kris and Betsy Smith</itunes:author>
      <link>http://www.croncast.com</link>
      <description>This is the keyword feed for Tweetair. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST.</description>
      <language>en-us</language>
	  <copyright>Palegroove Studios 2004-2013</copyright>
	  		<itunes:explicit>No</itunes:explicit>

		<itunes:keywords>Croncast, Kris, Betsy, Comedy, Parenting, Funny, Palegroove, Croncast, eBay, Goodwill</itunes:keywords>

		<itunes:subtitle>This is the keyword feed for Tweetair. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST.</itunes:subtitle>

 	<itunes:summary>This is the keyword feed for Tweetair. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST.</itunes:summary>

 	<image> 

		<url>http://www.croncast.com/images/croncast_itunes.jpg</url>
 		<title>Tweetair | Croncast - Life is Show Prep</title>
 		<link>http://www.croncast.com</link>
 		<description>This is the keyword feed for Tweetair. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST.</description>
 	</image> 	
	<itunes:image href="http://www.croncast.com/images/croncast_itunes.jpg" />
<itunes:category text="Comedy"/>
<itunes:category text="Society &amp; Culture">
</itunes:category>
<itunes:owner> 
			<itunes:name>Croncast - Kris and Betsy Smith</itunes:name>
	        <itunes:email>info@palegroove.com</itunes:email>
 </itunes:owner>
      <docs>http://www.croncast.com</docs>
      <generator>Palegroove</generator>
      <item>
         <title>Status of Tweetair</title>
         <link>http://www.croncast.com/rssk/1131/Status-of-Tweetair_Twitter-API_pages.php</link>
		 <category>Blog</category>
			<description><![CDATA[For those of you that were following my project, <a href="http://tweetair.com">tweetair</a>, it might appear that not much progress has been made. Unfortunately, there has been progress but not of the type that is conducive to bringing tweetair online.<br><br>Basing the main functionality of tweetair on the twitter API seemed to be a safe bet until I began working with it extensively. When I put the project down for about 3 weeks and came back to it some of the core functionality that tweetair requires had been removed. Not removed from the documentation but the API itself.<br><br>I found this out after a couple days. I thought it was my code that was causing the problem but after a message exchange with Alex at twitter he let me know that the feature had been turned off. He let me know that it should return, however, he doesn't know when. That's why they left my desired feature, pagination, in the API help docs. Turns out that I'm not crazy, I just didn't know.<br><br>The reason that pagination is so important is that it can return more than minimum of 20 results per API query. With pagination I could do multiple queries across 2-3 pages and get  40-60 results. A useful number that means fewer dropped tweets on an active channel. But the high number of results, as Alex stated, are the reason that pagination has been turned off.<br><br>It sucks, but I understand why. Twitter offers access to this API for free. And not just that but the impact that the API and extensive calls can have a major impact on Twitter's overall performance like locking up databases.<br><br>For what it's worth, if pagination comes back or new features are added to the API that make it possible to get more results then I will get back on tweetair full force. But until then I will move on to another small project and come back to it with the mind set of removing the Twitter connected piece and make it a standalone app.<br><br>Tags: <a href="http://www.croncast.com/key/Twitter API">Twitter API</a> <a href="http://www.technorati.com/tag/Twitter API"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Twitter API.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/pages">pages</a> <a href="http://www.technorati.com/tag/pages"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/pages.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Tweetair">Tweetair</a> <a href="http://www.technorati.com/tag/Tweetair"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Tweetair.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/API">API</a> <a href="http://www.technorati.com/tag/API"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/API.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/pagination">pagination</a> <a href="http://www.technorati.com/tag/pagination"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/pagination.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></description><content:encoded><![CDATA[For those of you that were following my project, <a href="http://tweetair.com">tweetair</a>, it might appear that not much progress has been made. Unfortunately, there has been progress but not of the type that is conducive to bringing tweetair online.<br><br>Basing the main functionality of tweetair on the twitter API seemed to be a safe bet until I began working with it extensively. When I put the project down for about 3 weeks and came back to it some of the core functionality that tweetair requires had been removed. Not removed from the documentation but the API itself.<br><br>I found this out after a couple days. I thought it was my code that was causing the problem but after a message exchange with Alex at twitter he let me know that the feature had been turned off. He let me know that it should return, however, he doesn't know when. That's why they left my desired feature, pagination, in the API help docs. Turns out that I'm not crazy, I just didn't know.<br><br>The reason that pagination is so important is that it can return more than minimum of 20 results per API query. With pagination I could do multiple queries across 2-3 pages and get  40-60 results. A useful number that means fewer dropped tweets on an active channel. But the high number of results, as Alex stated, are the reason that pagination has been turned off.<br><br>It sucks, but I understand why. Twitter offers access to this API for free. And not just that but the impact that the API and extensive calls can have a major impact on Twitter's overall performance like locking up databases.<br><br>For what it's worth, if pagination comes back or new features are added to the API that make it possible to get more results then I will get back on tweetair full force. But until then I will move on to another small project and come back to it with the mind set of removing the Twitter connected piece and make it a standalone app.<br><br>Tags: <a href="http://www.croncast.com/key/Twitter API">Twitter API</a> <a href="http://www.technorati.com/tag/Twitter API"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Twitter API.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/pages">pages</a> <a href="http://www.technorati.com/tag/pages"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/pages.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Tweetair">Tweetair</a> <a href="http://www.technorati.com/tag/Tweetair"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Tweetair.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/API">API</a> <a href="http://www.technorati.com/tag/API"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/API.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/pagination">pagination</a> <a href="http://www.technorati.com/tag/pagination"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/pagination.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></content:encoded>

         <pubDate>Tue, 06 Nov 2007 08:49:24 -0600</pubDate>         <guid isPermaLink="false">tag:croncast.com,1131</guid>

			<itunes:subtitle/>
				<itunes:summary>For those of you that were following my project, tweetair, it might appear that not much progress has been made. Unfortunately, there has been progress but not of the type that is conducive to bringing tweetair online.Basing the main functionality of tweetair on the twitter API seemed to be a safe bet until I began working with it extensively. When</itunes:summary>
				<itunes:explicit>no</itunes:explicit>
				<itunes:keywords>Twitter API, pages, Tweetair, API, pagination</itunes:keywords> 
      </item>
      <item>
         <title>Saturday code goodness means flickr, flafoo and twitter</title>
         <link>http://www.croncast.com/rssk/1056/Saturday-code-goodness-means-flickr-flafoo-and-twitter_TwitterGram_Dave-Winer.php</link>
		 <category>Blog</category>
			<description><![CDATA[So far I've got a new flickr + twitter script done and need to move on to flafoo while I have some daylight to burn.<br><br>The flickr + twitter code is why all of the pics have been showing up as posts and why all the people following me on twitter got blasted with 20 messages at once . . . sorry for that. I promptly setup a twitter account to test with.<br><br>For the last two months I have been sending photos from my phone to flickr and having them inserted as blog posts. Which has been pretty awesome and a ton of fun. But what I was missing was the twitter connection. Not anymore.<br><br>Now, thanks to <a href="http://www.scripting.com/stories/2007/10/04/integratingMultipleAppsAmp.html">this post</a> from Dave Winer and code that I had already written for <a href="http://tweetair.com">@tweetair</a> (coming very soon, I swear), <a href="http://www.flafoo.com">flafoo</a> and <a href="http://www.croncast.com">Croncast</a>, it took about ten minutes to get it up and running.<br><br>Dave's post was important because it turned the light for me. The "Ahaa" moment was when I realized I was already parsing my flickr feed every two minutes anyway looking for photos that I had marked to be blog posts. All I needed to do was differentiate what was to be a blog post from that of a twitter update.<br><br>It took about two seconds. <br><br>I make blog posts from flickr by starting a description of a photo with an asterisk, like so "*", and adding my content after that. For twitter I use "^" to tell the script to send a tweet. If I use them together "*^" then I get both.<br><br>Dave's setup with <a href="http://www.twittergram.com/flickrtotwitter">TwitterGram</a> is much cleaner, using only the tag portion to note that a flickr upload is meant to be a tweet, simple and clean. I  highly recommend it to anyone who wants to tweet their flickr photos with ease. My code is custom and considerably more messy for a guy that wants to have control over blog posts, blog posts and tweets or just tweets by uploading photos to flickr.<br><br>API's + the RSS 2.0 + curl + simplexml_load_file = ridiculously low threshold for a mediocre coder to join the integration party.<br><br>Speaking of API's, I will be updating <a href="http://flafoo.com">flafoo</a> today and possibly tomorrow with new categories that will henceforth be known as "flafoogeries" and the ability for anyone to add a "flafoogery" from the site.<br><br>Tags: <a href="http://www.croncast.com/key/TwitterGram">TwitterGram</a> <a href="http://www.technorati.com/tag/TwitterGram"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/TwitterGram.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Dave Winer">Dave Winer</a> <a href="http://www.technorati.com/tag/Dave Winer"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Dave Winer.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/twitter">twitter</a> <a href="http://www.technorati.com/tag/twitter"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/twitter.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/flickr">flickr</a> <a href="http://www.technorati.com/tag/flickr"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/flickr.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/flafoo">flafoo</a> <a href="http://www.technorati.com/tag/flafoo"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/flafoo.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></description><content:encoded><![CDATA[So far I've got a new flickr + twitter script done and need to move on to flafoo while I have some daylight to burn.<br><br>The flickr + twitter code is why all of the pics have been showing up as posts and why all the people following me on twitter got blasted with 20 messages at once . . . sorry for that. I promptly setup a twitter account to test with.<br><br>For the last two months I have been sending photos from my phone to flickr and having them inserted as blog posts. Which has been pretty awesome and a ton of fun. But what I was missing was the twitter connection. Not anymore.<br><br>Now, thanks to <a href="http://www.scripting.com/stories/2007/10/04/integratingMultipleAppsAmp.html">this post</a> from Dave Winer and code that I had already written for <a href="http://tweetair.com">@tweetair</a> (coming very soon, I swear), <a href="http://www.flafoo.com">flafoo</a> and <a href="http://www.croncast.com">Croncast</a>, it took about ten minutes to get it up and running.<br><br>Dave's post was important because it turned the light for me. The "Ahaa" moment was when I realized I was already parsing my flickr feed every two minutes anyway looking for photos that I had marked to be blog posts. All I needed to do was differentiate what was to be a blog post from that of a twitter update.<br><br>It took about two seconds. <br><br>I make blog posts from flickr by starting a description of a photo with an asterisk, like so "*", and adding my content after that. For twitter I use "^" to tell the script to send a tweet. If I use them together "*^" then I get both.<br><br>Dave's setup with <a href="http://www.twittergram.com/flickrtotwitter">TwitterGram</a> is much cleaner, using only the tag portion to note that a flickr upload is meant to be a tweet, simple and clean. I  highly recommend it to anyone who wants to tweet their flickr photos with ease. My code is custom and considerably more messy for a guy that wants to have control over blog posts, blog posts and tweets or just tweets by uploading photos to flickr.<br><br>API's + the RSS 2.0 + curl + simplexml_load_file = ridiculously low threshold for a mediocre coder to join the integration party.<br><br>Speaking of API's, I will be updating <a href="http://flafoo.com">flafoo</a> today and possibly tomorrow with new categories that will henceforth be known as "flafoogeries" and the ability for anyone to add a "flafoogery" from the site.<br><br>Tags: <a href="http://www.croncast.com/key/TwitterGram">TwitterGram</a> <a href="http://www.technorati.com/tag/TwitterGram"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/TwitterGram.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Dave Winer">Dave Winer</a> <a href="http://www.technorati.com/tag/Dave Winer"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Dave Winer.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/twitter">twitter</a> <a href="http://www.technorati.com/tag/twitter"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/twitter.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/flickr">flickr</a> <a href="http://www.technorati.com/tag/flickr"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/flickr.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/flafoo">flafoo</a> <a href="http://www.technorati.com/tag/flafoo"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/flafoo.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></content:encoded>

         <pubDate>Sat, 13 Oct 2007 16:31:21 -0500</pubDate>         <guid isPermaLink="false">tag:croncast.com,1056</guid>

			<itunes:subtitle/>
				<itunes:summary>So far I&#039;ve got a new flickr + twitter script done and need to move on to flafoo while I have some daylight to burn.The flickr + twitter code is why all of the pics have been showing up as posts and why all the people following me on twitter got blasted with 20 messages at once . . . sorry for that. I promptly setup a twitter account to test</itunes:summary>
				<itunes:explicit>no</itunes:explicit>
				<itunes:keywords>TwitterGram, Dave Winer, twitter, flickr, flafoo</itunes:keywords> 
      </item>
   </channel>
</rss>