[twitter-dev] Re: Streaming API: Spritzer-stream coverage
Makes sense. I was assuming the same. Thanks people! John from Twitter said that spritzer is 1/3 of the gardenhose, which makes it 15%. So I guess statistical insignificance of spritzer is due to its low percentage. Any explanation directly from Twitter? On May 26, 6:01 pm, stephane stephane.philipa...@gmail.com wrote: Hi Sven, well I merely assumed that the easiest way for twitter to send a subset of tweets on spitzer was to send them based on their ids (autoincrement integer)... watching at the stream, I noticed that all the ids where ending with 000,001,002,003,004, 100,102, ... 900,901,... 904 I did not push the analysis further though On May 26, 3:24 am, Sven Svensson twitterf...@gmail.com wrote: Hi Stephane, I used the following calculation to obtain a four percent estimate for the spritzer stream: tweets_seen_in_stream / (max_tweet_id_seen_in_stream - min_tweet_id_seen_in_stream) Did you use the same methodology? The four percent is probably a bit too low as I assume private tweets get tweet_id:s too, which makes the denominator a bit too large due to private tweets being included. On Mon, May 25, 2009 at 11:39 PM, stephane stephane.philipa...@gmail.com wrote: looking at the tweet ids it looks like the spitzer stream delivers 5 tweets every hundreds this would make it a 5% of the firehose am i correct? Stephane http://www.twazzup.com
[twitter-dev] Re: Paging for friends/ids
Thanks for looking into this! On May 26, 8:24 am, Matt Sanford m...@twitter.com wrote: Hi there, It certainly looks like a bug. I'll take a look at the issue. If you want updates as work progresses please visit the issue and mark it with a star (should be next to the title). Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 25, 2009, at 12:18 AM, elversatile wrote: Could somebody help me solve the paging dilemma? At least, tell me if it is a bug, or it is my misunderstanding of API? On May 22, 3:09 pm, elversatile elversat...@gmail.com wrote: It seems that paging is not working correctly for friends/ids call. I was trying to page through friends of Barack Obama by doinghttp://twitter.com/friends/ids/barackobama.xml?page=1,http://twitter ?page=2, etc. But it seems that every file just gets bigger, e.g., first I get 5000 ids, then 1, up to 20 when on page 40 and then it just stop working. I thought the intention was to page through friends 5000 ids at a time, instead it seems like it's giving me everything through that page number, until it can no longer fetch that many. Is it a known problem? Any way around this?
[twitter-dev] Re: Streaming API: Spritzer-stream coverage
How are spritzer statuses sampled? Are they picked uniformly at random? Or is there some logic behind it? Also, what makes it statistically insignificant? Is it its percentage in relation to the entire stream or the way it is sampled? Thanks, -Eldar On May 24, 8:23 pm, John Kalucki jkalu...@gmail.com wrote: Sven, Excluding connection ramp-up and ramp-down skew, each spritzer feed delivers the same statuses as all other spritzer feeds. Likewise, each gardenhose feed delivers the same statuses as all other gardenhose feeds. Also, spritzer feeds are a strict subset of gardenhose feeds. There's no point in consuming multiple sampled feeds (spritzer/ spritzer, gardenhose/spritzer, gardenhose/gardenhose), as you'll just receive duplicate data. Multiple sessions on sampled feeds just waste scarce resources and you also may find your access automatically limited for a period of time. Reduce, reuse, recycle! -John Kalucki Services, Twitter Inc. On May 24, 10:51 am, Sven Svensson twitterf...@gmail.com wrote: Thanks for an excellent API. I have two questions in relation to the streaming API: * Assume that two users are both reading the spritzer stream at the same time - will they get the same spritzer streams covering the same subset of all tweets, or will they get two separate spritzer streams covering different tweets? * Roughly what percentage of all tweets are distributed in the spritzer stream? Is it in the region of four percent of all tweets (my guesstimate)? Thanks!
[twitter-dev] Re: Paging for friends/ids
Could somebody help me solve the paging dilemma? At least, tell me if it is a bug, or it is my misunderstanding of API? On May 22, 3:09 pm, elversatile elversat...@gmail.com wrote: It seems that paging is not working correctly for friends/ids call. I was trying to page through friends of Barack Obama by doinghttp://twitter.com/friends/ids/barackobama.xml?page=1,http://twitter.com/friends/ids/barackobama.xml?page=2, etc. But it seems that every file just gets bigger, e.g., first I get 5000 ids, then 1, up to 20 when on page 40 and then it just stop working. I thought the intention was to page through friends 5000 ids at a time, instead it seems like it's giving me everything through that page number, until it can no longer fetch that many. Is it a known problem? Any way around this?
[twitter-dev] Paging for friends/ids
It seems that paging is not working correctly for friends/ids call. I was trying to page through friends of Barack Obama by doing http://twitter.com/friends/ids/barackobama.xml?page=1, http://twitter.com/friends/ids/barackobama.xml?page=2, etc. But it seems that every file just gets bigger, e.g., first I get 5000 ids, then 1, up to 20 when on page 40 and then it just stop working. I thought the intention was to page through friends 5000 ids at a time, instead it seems like it's giving me everything through that page number, until it can no longer fetch that many. Is it a known problem? Any way around this?
[twitter-dev] Data Mining timeline is empty
I have Data Mining public timeline returning empty statuses node (in XML). It was stuck for 30 or so hours before (just like for everybody else), but now I'm not getting anything back. Is this a general problem for everybody you guys are working on, is it something specific to my account?
[twitter-dev] Re: It looks like timelines and search are stuck
Confirming the same issue. I've been observing this for the last 24 hours or so. On May 13, 9:18 pm, Doug Williams d...@twitter.com wrote: Ops guys are on it, fixing a problem with back end machines. Thanks for the report. Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw On Wed, May 13, 2009 at 8:44 PM, Hayes Davis ha...@appozite.com wrote: Guys, I don't see any notice on the status blog or other official channels so I figured I might as well say something. None of my account timelines have updated in more than 45 minutes and all search queries I'm looking at are that old as well. Hayes
