Hey dude. You gave me a hint, but not tweetstream, that is twitterstream, which is newer and works for me.
On Fri, Feb 25, 2011 at 2:12 AM, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > On Thu, 24 Feb 2011 17:34:52 +0800, Chen Jack S Y <aquaj...@gmail.com> > wrote: > >> Thanks, dude. My problem is still there though. >> >> When I try the streaming api with "curl" in command line, everything >> goes well and it tracks a few thousands of ids successfully. >> >> While using eventmachine (together with em-http-request) ruby gem, >> haven't found any solutions to track more 400 ids but keep receiving >> 413 response errors. Kind of weird. >> > > Is this the "tweetstream" Ruby gem? If their repository is still on Github, > it hasn't been updated in over a year. In particular, they haven't added > code for User Streams or oAuth. Could they be using an incorrect endpoint or > something like that? > > -- > http://twitter.com/znmeb http://borasky-research.net > > "A mathematician is a device for turning coffee into theorems." -- Paul > Erdős > > -- > 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: > http://groups.google.com/group/twitter-development-talk > -- 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: http://groups.google.com/group/twitter-development-talk
