I have Site Streams implemented for a number of twitter accounts on my
testbed system. It is working like a charm, and for this system at
least, the home timeline, mentions and messages are all super fast
(obviously). It saves API calls, it is nice, I am pretty happy.

I wonder: What other data coming down the wire are most likely to save
API calls -- and are thus worth the effort to capture in the local
fast database for async processing? Other than tweets (including
mentions) and messages (DMs)....



Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to