caching feeds | Croncast - Life is Show Prep Kris and Betsy Smith http://www.croncast.com This is the keyword feed for caching feeds. 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. en-us Palegroove Studios 2004-2010 No Croncast, Kris, Betsy, Comedy, Parenting, Funny, Palegroove, Croncast, eBay, Goodwill This is the keyword feed for caching feeds. 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. This is the keyword feed for caching feeds. 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. http://www.croncast.com/images/croncast_itunes.jpg caching feeds | Croncast - Life is Show Prep http://www.croncast.com This is the keyword feed for caching feeds. 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. Croncast - Kris and Betsy Smith info@palegroove.com http://www.croncast.com Palegroove Feedage - Google Reader shared feed update http://www.croncast.com/rssk/896/Feedage---Google-Reader-shared-feed-update_Feed-Forager_RSS-feed-directory.php Blog Feedage.

Showing up in a splog or other site that pulls content into it via RSS feed isn't that out of the norm these days. What got my attention though was that it wasn't just an item from a post it was the entire feed. And not just any feed but one of my Google Reader keyword shared feeds. It's pretty cool to see them propagating after only about a week after coming into existence.

After a cursory review of the Feedage site it turns out to be a RSS feed directory. They send out their Feed Forager spider, grab a feed and index it (maybe, I haven't figured this out yet - see number 2 below). Turns out that the Feed Forager grabbed a feed from my shared items page was for everything that I have read about memory.

The funny part is that I haven't read any content specifically about memory. I've read articles that include the word memory but nothing about brain science, how to improve you memory or loss thereof. Turns out my memory feed at this stage is pretty useless. Maybe I need to step it up and get some science feeds in my reader!

Interesting points:

1. Shared item keyword feeds have only been active on my site for one week
2. Feedage doesn't appear to be caching feeds but if they are they're pinging the feed on refresh and re-indexing it
3. Feedage allows you to rate the feed's content with a 5 star system
4. Rating in the star system creates a grade system A-D with an appropriate icon next to the feed
5. Not all my Google Reader shared keyword feeds are as contextually relevant as one about "itunes".

Tags: Feed Forager RSS feed directory Feedage Google Reader shared rss feeds ]]>Feedage.

Showing up in a splog or other site that pulls content into it via RSS feed isn't that out of the norm these days. What got my attention though was that it wasn't just an item from a post it was the entire feed. And not just any feed but one of my Google Reader keyword shared feeds. It's pretty cool to see them propagating after only about a week after coming into existence.

After a cursory review of the Feedage site it turns out to be a RSS feed directory. They send out their Feed Forager spider, grab a feed and index it (maybe, I haven't figured this out yet - see number 2 below). Turns out that the Feed Forager grabbed a feed from my shared items page was for everything that I have read about memory.

The funny part is that I haven't read any content specifically about memory. I've read articles that include the word memory but nothing about brain science, how to improve you memory or loss thereof. Turns out my memory feed at this stage is pretty useless. Maybe I need to step it up and get some science feeds in my reader!

Interesting points:

1. Shared item keyword feeds have only been active on my site for one week
2. Feedage doesn't appear to be caching feeds but if they are they're pinging the feed on refresh and re-indexing it
3. Feedage allows you to rate the feed's content with a 5 star system
4. Rating in the star system creates a grade system A-D with an appropriate icon next to the feed
5. Not all my Google Reader shared keyword feeds are as contextually relevant as one about "itunes".

Tags: Feed Forager RSS feed directory Feedage Google Reader shared rss feeds ]]> Mon, 03 Sep 2007 10:25:52 -0400 tag:croncast.com,896 I got an ego update from Google this morning that my name had shown up in a post at a site called Feedage. Showing up in a splog or other site that pulls content into it via RSS feed isn't that out of the norm these days. What got my attention though was that it wasn't just an item from a post it was the entire feed. And not just any feed no Feed Forager, RSS feed directory, Feedage, Google Reader, shared rss feeds Podshow caching and how to stop it http://www.croncast.com/rssk/416/Podshow-caching-and-how-to-stop-it_Podshow_PDN.php Blog Three months ago I created a podcast management system. Part of that development was tracking everything that happens with all files, especially RSS. Being a huge stats nerd I freaked when I kept getting regular hits from this ip: 72.3.228.221 to my main RSS feed where the User Agent was null. WTF, a null user agent?

So a little due diligence I found the IP is part of Podshow's block at RackSpace. I skype Chris from Podcast Alley, cause I knew him way back before Podshow, and asked him what was up. Oh yeah, the IP was asking for authentication when I visited so I couldn't see what going on.

I asked him what they were doing with the feeds. His reply was that they were caching them. No big deal. Still problematic in a sense that I am not pinging them to send them an update, but whatever, they got a plan and caching isn't inherintly evil. At this time I requested him to add the User Agent information to the script they were using to pull the feeds. That never happened.

Needless to say I shared this information with a couple of podcasters who immediately blocked the the IP address. But I didn't. So for the last three months they have been hitting not only my feed but the feeds of many other people every half hour and caching them.

But this is where the problem comes in. Yesterday with the botched launch of the new Podshow+. I took a look at the IP which was no longer asking for authentication and took a look around. I look at it like if my feed is public and you are using it in your site and your IP is public and broadcast to my database I can use it too. So I took a look around. Yikes!

I found my feed . . . or did I? What I found as others are finding or any podcaster whether they belong to the network or are paid by podshow is that they are re-writing the cached feeds!! Yup. Changing tags, truncating data, modifying the RSS generator tag to say "Podshow Delivery Network" (Update: it reads "PodShow PDN") and . . . and rewriting the original URL of the feed that they cached. Are you kidding? They don't even link to my original feed. So how would I know people are even subscribed? I wouldn't and they would. More incentive to join their network I guess.

If people weren't sure about Podshow's intent to make money off the back of every podcaster then this is a sure sign that if they did't they sure do now. The fact that Podshow is purporting even at this early stage to be the proprietor of all podcasters is a joke. The arrogance to think that we all somehow owe them or should allow them to rewrite our feeds because their network is the be all end all signals that this is the end for them.

If you would like to stop Podshow from caching your feed and rewriting it as they roll Podcast Alley, Podsafe Music Network and the Podshow home page into the mega Podshow+ PDN then block this IP: 72.3.228.221.

Update: It appears as of 12 a.m. on July 7th the Podshow caching bot or script was turned off. But have some fun checking your logs for their IP address I bet it's there.

Update two: If you would like to see some screen shots and read more of this discussion check out Michael Geoghegan's post or Todd Cochrane's. For some other good opinions, Paul Colligan's "Podshow Hysterics" post and this one from FuzzyBlog. It will be interesting to see where this conversation goes today as this picks up some steam.

Final update then new post: 9:31 a.m. July 7 - Podshow is scraping from the ip again so lets have some fun.

Final final update: 2:05 p.m. July 7 - The XML chicklet link now goes to podcaster's original feeds.

Tags: Podshow PDN caching feeds rewriting feeds 72.3.228.221 ]]>Three months ago I created a podcast management system. Part of that development was tracking everything that happens with all files, especially RSS. Being a huge stats nerd I freaked when I kept getting regular hits from this ip: 72.3.228.221 to my main RSS feed where the User Agent was null. WTF, a null user agent?

So a little due diligence I found the IP is part of Podshow's block at RackSpace. I skype Chris from Podcast Alley, cause I knew him way back before Podshow, and asked him what was up. Oh yeah, the IP was asking for authentication when I visited so I couldn't see what going on.

I asked him what they were doing with the feeds. His reply was that they were caching them. No big deal. Still problematic in a sense that I am not pinging them to send them an update, but whatever, they got a plan and caching isn't inherintly evil. At this time I requested him to add the User Agent information to the script they were using to pull the feeds. That never happened.

Needless to say I shared this information with a couple of podcasters who immediately blocked the the IP address. But I didn't. So for the last three months they have been hitting not only my feed but the feeds of many other people every half hour and caching them.

But this is where the problem comes in. Yesterday with the botched launch of the new Podshow+. I took a look at the IP which was no longer asking for authentication and took a look around. I look at it like if my feed is public and you are using it in your site and your IP is public and broadcast to my database I can use it too. So I took a look around. Yikes!

I found my feed . . . or did I? What I found as others are finding or any podcaster whether they belong to the network or are paid by podshow is that they are re-writing the cached feeds!! Yup. Changing tags, truncating data, modifying the RSS generator tag to say "Podshow Delivery Network" (Update: it reads "PodShow PDN") and . . . and rewriting the original URL of the feed that they cached. Are you kidding? They don't even link to my original feed. So how would I know people are even subscribed? I wouldn't and they would. More incentive to join their network I guess.

If people weren't sure about Podshow's intent to make money off the back of every podcaster then this is a sure sign that if they did't they sure do now. The fact that Podshow is purporting even at this early stage to be the proprietor of all podcasters is a joke. The arrogance to think that we all somehow owe them or should allow them to rewrite our feeds because their network is the be all end all signals that this is the end for them.

If you would like to stop Podshow from caching your feed and rewriting it as they roll Podcast Alley, Podsafe Music Network and the Podshow home page into the mega Podshow+ PDN then block this IP: 72.3.228.221.

Update: It appears as of 12 a.m. on July 7th the Podshow caching bot or script was turned off. But have some fun checking your logs for their IP address I bet it's there.

Update two: If you would like to see some screen shots and read more of this discussion check out Michael Geoghegan's post or Todd Cochrane's. For some other good opinions, Paul Colligan's "Podshow Hysterics" post and this one from FuzzyBlog. It will be interesting to see where this conversation goes today as this picks up some steam.

Final update then new post: 9:31 a.m. July 7 - Podshow is scraping from the ip again so lets have some fun.

Final final update: 2:05 p.m. July 7 - The XML chicklet link now goes to podcaster's original feeds.

Tags: Podshow PDN caching feeds rewriting feeds 72.3.228.221 ]]> Thu, 06 Jul 2006 23:06:38 -0400 tag:croncast.com,416 Three months ago I created a podcast management system. Part of that development was tracking everything that happens with all files, especially RSS. Being a huge stats nerd I freaked when I kept getting regular hits from this ip: 72.3.228.221 to my main RSS feed where the User Agent was null. WTF, a null user agent?So a little due diligence I no Podshow, PDN, caching feeds, rewriting feeds, 72.3.228.221