<?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>dynamic rss | 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 dynamic rss. 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 dynamic rss. 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 dynamic rss. 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>dynamic rss | Croncast - Life is Show Prep</title>
 		<link>http://www.croncast.com</link>
 		<description>This is the keyword feed for dynamic rss. 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>And you're a giant nerd.</title>
         <link>http://www.croncast.com/rssk/892/And-youre-a-giant-nerd_giant-nerd_google-rss.php</link>
		 <category>Blog</category>
			<description><![CDATA[<a href="http://yourmonkeycalled.com/">Scott</a> appears to be correct.<br><br>He sent me an email yesterday to say that he and Pete had a conversation about something. Which evidently happens on occasion. From the email and attached screen shot I deduced that the discussion was about Google indexing RSS feeds and linking directly to them and how that sucks. 'Cause it does.<br><br>Don't get me wrong I love Google for indexing feeds. Seriously, it rocks. They are leading in this area.<br><br>Let me show you what's going on:<br><br>1. Scott searches at Google for an awesome party in Chicago called <a href="http://www.google.com/search?q=The+Deaf+Chicago+Party" target="_blank">"The Deaf Chicago Party"</a> (remind me to ask him about this) and the first result is Croncast.<br><br><a href="http://www.google.com/search?q=The+Deaf+Chicago+Party" target="_blank"><img src="http://www.croncast.com/images/search_and_rss_1.jpg" border="0"></a><br><br>The first thing to pay attention to in this image to pay attention to is the green URL - <a href="http://www.croncast.com/keyrss/Chicago party.rss" target="_blank">http://www.croncast.com/keyrss/Chicago party.rss</a>. Yep, it's a RSS feed and not a web page. To which I say, "right on." However, 99.9 times out of 100 when  when someone clicks through and RSS link in Google they get a face full of XML or an ugly feed. Click the link above to see.<br><br>2. Scott clicked on my link to the RSS from Google and and something magical happened. See the screen shot that he sent me:<br><br><img src="http://www.croncast.com/images/search_and_rss_2.jpg"><br><br>He ended up at my site not looking at a bunch of XML or having his browser ask him if he wants to subscribe to my feed. He was taken directly to a page within my site that has relevant posts from our podcast and blog for the topic he was looking for . . . maybe, probably not really since I don't know what 'The Deaf Chicago Party' is. And, apparently, Google doesn't either. Let's just call it serendipity.<br><br>The summary to my detective work can be boiled down to what I figured out a few months ago:<br><br>
1. Google loves RSS feeds filled with new stuff<br>
2. I love RSS feeds filled with my new and old stuff<br>
3. People like information on topics of interest<br>
4. I created RSS feeds by post tag but also allow them to be created by readers/listeners dynamically (see #3)<br>
5. I did some quick SEO on these feeds to make their titles and descriptions relevant to topic<br>
6. Finally, I coded the feeds to check if user was coming from Google or other search engines<br>
7. Google sends bot and indexes said feeds<br>
8. Someone searches at Google for a topic like <a href="http://www.google.com/search?hl=en&safe=off&q=tijuana+vasectomy" target="_blank">"tijuana vasectomy"</a> - just got a hit for it yesterday<br>
9. That someone clicks the link and ends up at site with the exact same items in it that were in the RSS feed without all the feed related hassle<br><br>It's not a perfect system but one that I think is way more acceptable to a user than clicking a link in a search engine and getting put into a feed. In many cases being dumped into a feed isn't going to get you to the content you wanted anyway because it has been pushed out by newer items. When I put someone into my site from a feed result in a search engine they then have the ability to find their topic right there. If not, they an internal site search that will find what they are after. The coolest part to me about it is that once they have made it to the site I then offer them the feed for their topic, just in case this is truly what they were after.<br><br>Tags: <a href="http://www.croncast.com/key/giant nerd">giant nerd</a> <a href="http://www.technorati.com/tag/giant nerd"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/giant nerd.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/google rss">google rss</a> <a href="http://www.technorati.com/tag/google rss"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/google rss.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/keyword rss feeds">keyword rss feeds</a> <a href="http://www.technorati.com/tag/keyword rss feeds"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/keyword rss feeds.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/dynamic rss">dynamic rss</a> <a href="http://www.technorati.com/tag/dynamic rss"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/dynamic rss.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/tijuana vasectomy">tijuana vasectomy</a> <a href="http://www.technorati.com/tag/tijuana vasectomy"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/tijuana vasectomy.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></description><content:encoded><![CDATA[<a href="http://yourmonkeycalled.com/">Scott</a> appears to be correct.<br><br>He sent me an email yesterday to say that he and Pete had a conversation about something. Which evidently happens on occasion. From the email and attached screen shot I deduced that the discussion was about Google indexing RSS feeds and linking directly to them and how that sucks. 'Cause it does.<br><br>Don't get me wrong I love Google for indexing feeds. Seriously, it rocks. They are leading in this area.<br><br>Let me show you what's going on:<br><br>1. Scott searches at Google for an awesome party in Chicago called <a href="http://www.google.com/search?q=The+Deaf+Chicago+Party" target="_blank">"The Deaf Chicago Party"</a> (remind me to ask him about this) and the first result is Croncast.<br><br><a href="http://www.google.com/search?q=The+Deaf+Chicago+Party" target="_blank"><img src="http://www.croncast.com/images/search_and_rss_1.jpg" border="0"></a><br><br>The first thing to pay attention to in this image to pay attention to is the green URL - <a href="http://www.croncast.com/keyrss/Chicago party.rss" target="_blank">http://www.croncast.com/keyrss/Chicago party.rss</a>. Yep, it's a RSS feed and not a web page. To which I say, "right on." However, 99.9 times out of 100 when  when someone clicks through and RSS link in Google they get a face full of XML or an ugly feed. Click the link above to see.<br><br>2. Scott clicked on my link to the RSS from Google and and something magical happened. See the screen shot that he sent me:<br><br><img src="http://www.croncast.com/images/search_and_rss_2.jpg"><br><br>He ended up at my site not looking at a bunch of XML or having his browser ask him if he wants to subscribe to my feed. He was taken directly to a page within my site that has relevant posts from our podcast and blog for the topic he was looking for . . . maybe, probably not really since I don't know what 'The Deaf Chicago Party' is. And, apparently, Google doesn't either. Let's just call it serendipity.<br><br>The summary to my detective work can be boiled down to what I figured out a few months ago:<br><br>
1. Google loves RSS feeds filled with new stuff<br>
2. I love RSS feeds filled with my new and old stuff<br>
3. People like information on topics of interest<br>
4. I created RSS feeds by post tag but also allow them to be created by readers/listeners dynamically (see #3)<br>
5. I did some quick SEO on these feeds to make their titles and descriptions relevant to topic<br>
6. Finally, I coded the feeds to check if user was coming from Google or other search engines<br>
7. Google sends bot and indexes said feeds<br>
8. Someone searches at Google for a topic like <a href="http://www.google.com/search?hl=en&safe=off&q=tijuana+vasectomy" target="_blank">"tijuana vasectomy"</a> - just got a hit for it yesterday<br>
9. That someone clicks the link and ends up at site with the exact same items in it that were in the RSS feed without all the feed related hassle<br><br>It's not a perfect system but one that I think is way more acceptable to a user than clicking a link in a search engine and getting put into a feed. In many cases being dumped into a feed isn't going to get you to the content you wanted anyway because it has been pushed out by newer items. When I put someone into my site from a feed result in a search engine they then have the ability to find their topic right there. If not, they an internal site search that will find what they are after. The coolest part to me about it is that once they have made it to the site I then offer them the feed for their topic, just in case this is truly what they were after.<br><br>Tags: <a href="http://www.croncast.com/key/giant nerd">giant nerd</a> <a href="http://www.technorati.com/tag/giant nerd"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/giant nerd.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/google rss">google rss</a> <a href="http://www.technorati.com/tag/google rss"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/google rss.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/keyword rss feeds">keyword rss feeds</a> <a href="http://www.technorati.com/tag/keyword rss feeds"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/keyword rss feeds.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/dynamic rss">dynamic rss</a> <a href="http://www.technorati.com/tag/dynamic rss"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/dynamic rss.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/tijuana vasectomy">tijuana vasectomy</a> <a href="http://www.technorati.com/tag/tijuana vasectomy"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/tijuana vasectomy.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></content:encoded>

         <pubDate>Thu, 30 Aug 2007 10:51:23 -0500</pubDate>         <guid isPermaLink="false">tag:croncast.com,892</guid>

			<itunes:subtitle/>
				<itunes:summary>Scott appears to be correct.He sent me an email yesterday to say that he and Pete had a conversation about something. Which evidently happens on occasion. From the email and attached screen shot I deduced that the discussion was about Google indexing RSS feeds and linking directly to them and how that sucks. &#039;Cause it does.Don&#039;t get me</itunes:summary>
				<itunes:explicit>no</itunes:explicit>
				<itunes:keywords>giant nerd, google rss, keyword rss feeds, dynamic rss, tijuana vasectomy</itunes:keywords> 
      </item>
      <item>
         <title>Maybe it isn't just Bloglines</title>
         <link>http://www.croncast.com/rssk/887/Maybe-it-isnt-just-Bloglines_dynamic-rss-ads_Bloglines.php</link>
		 <category>Blog</category>
			<description><![CDATA[I just got a heads up message from <a href="http://www.rklau.com/tins">Rick</a>, thanks Rick, that some more of you besides the Bloglines people might be having constant post update issues for posts that you have already read. Things like they show up as new entries.<br><br>If you experiencing this problem (which has probably been for the last two months, yikes) with your reader let me know. Send me a message with the reader name and the URL of the feed(s) you are subscribed to and I will look into it.<br><br>I did test these dynamic ads with Google Reader, NewsGator, FeedDemon, Rojo, IE 7, Thunderbird and tons of podcast aggregators. Obviously, not enough testing.<br><br>I am still of the mindset that reader makers need to fix the problem of multiple updates being displayed as new items. I can understand marking the item unread if it is read or notating the item has been updated, but am lost at adding it as a new unread entry every time they ping the feed.<br><br>Tags: <a href="http://www.croncast.com/key/dynamic rss ads">dynamic rss ads</a> <a href="http://www.technorati.com/tag/dynamic rss ads"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/dynamic rss ads.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Bloglines">Bloglines</a> <a href="http://www.technorati.com/tag/Bloglines"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Bloglines.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/constant updates">constant updates</a> <a href="http://www.technorati.com/tag/constant updates"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/constant updates.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Bloglines/3.1">Bloglines/3.1</a> <a href="http://www.technorati.com/tag/Bloglines/3.1"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Bloglines/3.1.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/rss time stamp">rss time stamp</a> <a href="http://www.technorati.com/tag/rss time stamp"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/rss time stamp.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></description><content:encoded><![CDATA[I just got a heads up message from <a href="http://www.rklau.com/tins">Rick</a>, thanks Rick, that some more of you besides the Bloglines people might be having constant post update issues for posts that you have already read. Things like they show up as new entries.<br><br>If you experiencing this problem (which has probably been for the last two months, yikes) with your reader let me know. Send me a message with the reader name and the URL of the feed(s) you are subscribed to and I will look into it.<br><br>I did test these dynamic ads with Google Reader, NewsGator, FeedDemon, Rojo, IE 7, Thunderbird and tons of podcast aggregators. Obviously, not enough testing.<br><br>I am still of the mindset that reader makers need to fix the problem of multiple updates being displayed as new items. I can understand marking the item unread if it is read or notating the item has been updated, but am lost at adding it as a new unread entry every time they ping the feed.<br><br>Tags: <a href="http://www.croncast.com/key/dynamic rss ads">dynamic rss ads</a> <a href="http://www.technorati.com/tag/dynamic rss ads"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/dynamic rss ads.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Bloglines">Bloglines</a> <a href="http://www.technorati.com/tag/Bloglines"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Bloglines.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/constant updates">constant updates</a> <a href="http://www.technorati.com/tag/constant updates"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/constant updates.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/Bloglines/3.1">Bloglines/3.1</a> <a href="http://www.technorati.com/tag/Bloglines/3.1"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/Bloglines/3.1.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a> <a href="http://www.croncast.com/key/rss time stamp">rss time stamp</a> <a href="http://www.technorati.com/tag/rss time stamp"><img src="http://www.croncast.com/images/technorati.gif" border="0"></a><a href="http://www.croncast.com/keyrss/rss time stamp.rss"><img src="http://www.croncast.com/images/c4_rss_tiny.jpg" border="0"></a>]]></content:encoded>

         <pubDate>Sat, 25 Aug 2007 20:14:38 -0500</pubDate>         <guid isPermaLink="false">tag:croncast.com,887</guid>

			<itunes:subtitle/>
				<itunes:summary>I just got a heads up message from Rick, thanks Rick, that some more of you besides the Bloglines people might be having constant post update issues for posts that you have already read. Things like they show up as new entries.If you experiencing this problem (which has probably been for the last two months, yikes) with your reader let me know.</itunes:summary>
				<itunes:explicit>no</itunes:explicit>
				<itunes:keywords>dynamic rss ads, Bloglines, constant updates, Bloglines/3.1, rss time stamp</itunes:keywords> 
      </item>
   </channel>
</rss>