Also note that the safer way to do what (I think) you're trying to do is to use the retweets API (http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retweets), for example
curl -uyouruser:yourpassword api.twitter.com/1/statuses/retweets/5865706501.xml ---Mark On Thu, Nov 19, 2009 at 2:08 PM, Mark McBride <[email protected]> wrote: > Great! I checked through the code paths, and they look solid on our end. > > ---Mark > > On Thu, Nov 19, 2009 at 1:24 PM, Jim Gilliam <[email protected]> wrote: >> I figured out what's happening. When "RT @thekabira" gets added to the >> front of the tweet, it makes the tweet text longer than 140 characters, so >> it then cuts off the rest of the tweet, which is what had "act" in it, so it >> never shows up through the streaming api tracking for anything with "act" in >> it. >> >> So this tweet: "What’s the deal with the Climate Bill? RT new >> #climategraphic, win a prize! http://bit.ly/12H1X7 via @PhaedraEL >> http://act.ly/Rxt"; >> >> turns into this, when it's retweeted: >> >> "RT @thekabira: What’s the deal with the Climate Bill? RT new >> #climategraphic, win a prize! http://bit.ly/12H1X7 via @PhaedraEL http://ac >> ..." >> >> Jim >> >> On Thu, Nov 19, 2009 at 12:05 PM, Jim Gilliam <[email protected]> wrote: >>> >>> My understanding is that the only way to get all the new retweets is >>> through the streaming API because they don't show up in search. So I'm >>> using the track method, but I'm not seeing retweets come through. >>> >>> Specifically, this: http://twitter.com/thekabira/status/5865706501 was >>> retweeted twice, but I didn't see it come through. Old style retweets >>> continue to come through normally. >>> >>> Jim Gilliam >>> http://act.ly/ >>> http://twitter.com/jgilliam >> >> >
