|
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 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.
|
|
|
|
| |
|
