Kris and Betsy Smith http://www.croncast.com This is the keyword feed for pagination. 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-2013 No Croncast, Kris, Betsy, Comedy, Parenting, Funny, Palegroove, Croncast, eBay, Goodwill This is the keyword feed for pagination. 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 pagination. 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 http://www.croncast.com This is the keyword feed for pagination. 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 http://www.croncast.com/rssk/1285/Google-Reader-shared-feeds-getting-tweaked_Google_shared-feeds.php Blog
Previously all content was delivered via the 'summary' namespace but when I did a check after getting some null data fields I took a look at the shared feed and sure enough there was a new namespace, 'content' for the main content. Makes sense. But it is a pain if you are expecting everything to be returned as 'summary'.

My guess is that they are saving time and money by not rewriting the original source feed main content namspace. However, it creates an XML namespace soup that is harder to navigate.

When stuff like this happens it makes me nervous, especially when I am building something on the back of it.

The last time this happened Twitter turned off pagination for getting recent tweets for your friends. Killing a really cool project that I spent more time than I care to recount. I'm hoping that Google will not do the same. Fingers crossed.

Tags: Google shared feeds namespace XML soup shared RSS ]]>
Previously all content was delivered via the 'summary' namespace but when I did a check after getting some null data fields I took a look at the shared feed and sure enough there was a new namespace, 'content' for the main content. Makes sense. But it is a pain if you are expecting everything to be returned as 'summary'.

My guess is that they are saving time and money by not rewriting the original source feed main content namspace. However, it creates an XML namespace soup that is harder to navigate.

When stuff like this happens it makes me nervous, especially when I am building something on the back of it.

The last time this happened Twitter turned off pagination for getting recent tweets for your friends. Killing a really cool project that I spent more time than I care to recount. I'm hoping that Google will not do the same. Fingers crossed.

Tags: Google shared feeds namespace XML soup shared RSS ]]> Thu, 03 Jan 2008 19:00:32 -0600 tag:croncast.com,1285 This afternoon I noticed something funny happening with Google Reader shared feeds. It seems that feeds are now mixing namespaces for the main content of the posts. Previously all content was delivered via the 'summary' namespace but when I did a check after getting some null data fields I took a look at the shared feed and sure enough no Google, shared feeds, namespace, XML soup, shared RSS http://www.croncast.com/rssk/1131/Status-of-Tweetair_Twitter-API_pages.php Blog 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 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.

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.

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.

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.

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.

Tags: Twitter API pages Tweetair API pagination ]]>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 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.

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.

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.

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.

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.

Tags: Twitter API pages Tweetair API pagination ]]> Tue, 06 Nov 2007 08:49:24 -0600 tag:croncast.com,1131 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 no Twitter API, pages, Tweetair, API, pagination