Re: [twitter-dev] Streaming API with start_date and end_date

This is not within the scope of the real-time streaming API which serves the purpose of streaming tweets & related events as they happen with very limited support for any kind of rewind behavior. On Thu, Jun 23, 2011 at 9:42 AM, Trevor Dean wrote: > This would be a great feature, any word on thi

Re: [twitter-dev] Streaming API with start_date and end_date

This would be a great feature, any word on this yet? Trevor Dean | Director big time design & communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-06-23, at 7:13 AM, JackRabbit wrote: > Hi Guys, > > is it possible to query streaming api with filter a

Re: [twitter-dev] Streaming API w/ two dedicated IP's

Connecting from two IPs, with two different users will be perfectly fine and fall within the current rules. On 14 Jun 2011, at 20:39, @dbbradle wrote: > It is kosher to connect to the Twitter Streaming API using two > dedicated IP's on two separate servers or does this violate the terms > of usa

Re: [twitter-dev] Streaming API, Following just a couple of people

Hi Ray, There isn't a buffer that has to be filled before the Streaming API delivers tweets. Only public tweets created after you open a connection will be delivered. Have the users you are following Tweeted since you connected, and are they public accounts (not protected)? On Jun 6, 2011, at

Re: [twitter-dev] Streaming API, Following just a couple of people

Hey Ray, As soon as the connection is established, you start receiving public statuses that match your filter predicates. Are you sure these users were actually tweeting during the time you were consuming the stream? Arnaud / @rno On Mon, Jun 6, 2011 at 6:04 AM, Ray Sl

Re: [twitter-dev] Streaming API credentials

You would create a twitter app at https://dev.twitter.com/apps After you create it, there is a "My Access Token" button on the details page for your application. I /believe/ that will get you what you want. James On Mon, May 23, 2011 at 3:04 PM, Craig Walls wrote: > > I'd like to use the strea

Re: [twitter-dev] Streaming API timeout issues

Hey there, Please be careful when you share pieces of code on this Mailing List. I had to reset your Twitter password because you just shared it publicly. Please go to http://twitter.com/account/resend_password so we can send you password reset instructions. Concerning your issue, the Streaming A

Re: [twitter-dev] Streaming API length

No. On 19 May 2011, at 20:26, Tereno wrote: > Hi there, > > Is there a maximum limit on how long we can maintain the connection to > the Streaming API or on the number of tweets consumed? > > Thanks -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-05

Re: [twitter-dev] Streaming API truncating tweets

Where are you seeing this truncation? Can you share some examples of the JSON with the truncated (I assume status body) field? In the case of retweets in the streaming API, you may see the top-level "text" node with truncated tweet text prepended with "RT " -- but the full text of the original ref

Re: [twitter-dev] Streaming API JSON Samples

>From "sample" you will receive "delete" messages. From User Streams you will receive numerous types of events, as well as tweets and DMs. I haven't looked at the documentation recently, but last time I did Twitter was still reserving the right to "add" message types and recommended you have a code

Re: [twitter-dev] Streaming API JSON Samples

Hi Juliano, >From filter stream we received just two types of messages: 'status' (tweets itself) and 'limit' (show how many tweets was suppressed since last reconnection). Abraços da UFRGS!! On Sun, May 1, 2011 at 3:40 PM, Juliano Bortolozzo Solanho < juliano.sola...@gmail.com> wrote: > Hello t

Re: [twitter-dev] Streaming API statuses/fileter method, "follow" parameter

With the "follow" parameter, you should only get "real" replies & retweets. If you need to track all mentions, try the "track" parameter (i.e. track=@user) Arnaud / @rno On Tue, Apr 19, 2011 at 9:35 PM, Kumar wrote: > Hi All, > > The streaming api documentation says t

Re: [twitter-dev] Streaming API Rate Limiting

On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos wrote: > No it won't. Streaming has rate limit with around 1% of firehose, if your > search term os too much generic. > If your search term or bouding box get too many tweets, you will start > receive 'limit' status message as doc said. > http://dev.

Re: [twitter-dev] Streaming API Rate Limiting

No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses On Th

Re: [twitter-dev] Streaming API Rate Limiting

On Thu, Mar 31, 2011 at 1:49 PM, Data Gatherer wrote: ... > I would not like the data gathering for one project to affect another > project. If I'm rate limited depending on how much data my single > connection to the data stream receives - this would affect all > projects. If this is the case, ca

Re: [twitter-dev] Streaming API access level limit

>From the developer resource, it is said that 'Each account may create only one standing connection to the Streaming API'. While it is possible to have a few streams with different users' account through OAuth? If yes, what's the limit? Thanks, J On Tue, Mar 1, 2011 at 4:25 AM, Matt Harris wrote

Re: [twitter-dev] Streaming API access level limit

Although this is specified at streaming API docs, it's possible to connect two diferent users at the same IP address. On Mon, Feb 28, 2011 at 5:25 PM, Matt Harris wrote: > Hi J, > > Glad you worked it out. The Streaming API (stream.twitter.com) does not > support multiple streams - only one conne

Re: [twitter-dev] Streaming API access level limit

Hi J, Glad you worked it out. The Streaming API (stream.twitter.com) does not support multiple streams - only one connection is permitted. This is explained in more detail on our developer resources site: http://dev.twitter.com/pages/streaming_api_concepts#access-rate-limiting Best, @thematth

Re: [twitter-dev] Streaming API access level limit

Thanks, figured it out. Another question, how many connections are allowed with a shared IP? Any suggestions on multiple streams in one machine with one IP? J On Mon, Feb 28, 2011 at 1:50 PM, John Kalucki wrote: > Are you specifying the IDs in the URL or in a POST parameter? There's a > limit t

Re: [twitter-dev] Streaming API limits...

John, Thank you for getting back to me. The doc lists a "For example, reconnect no more than twice every four minutes, or three times per six minutes, or some similar metric." but doesn't give a "Don't reconnect more than a few times a minute unless you are retrying automatically due to failur

Re: [twitter-dev] Streaming API limits...

This is documented in painful detail here: http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates . If you connect a second time, you should get a TCP Close or Reset on the first connection. It sounds like your client library isn't detecting the connection close. -John Kal

Re: [twitter-dev] Streaming API access level limit

Are you specifying the IDs in the URL or in a POST parameter? There's a limit to the URL length that we'll parse, but we'll take huge POST parameters. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Feb 22, 2011 at 11:22 PM, aquajach wrote: > Hi, > > Just started to play with s

Re: [twitter-dev] Streaming API access level limit

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 > wrote: > >> Thanks, dude. My problem is st

Re: [twitter-dev] Streaming API access level limit

On Thu, 24 Feb 2011 17:34:52 +0800, Chen Jack S Y 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) ru

Re: [twitter-dev] Streaming API access level limit

If it's working for you in curl, then it's likely something either in your code or the library you're using. Are you using OAuth to authenticate or basic auth? Either way, if you can get a trace of the exact POST body and URL you are sending when issuing the request from eventmachine, it will likel

Re: [twitter-dev] Streaming API access level limit

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 bu

Re: [twitter-dev] Streaming API access level limit

Hi J, The authoritative information for the Streaming API is under the /pages/ path and you should use that for guidance. The number of connections you are allowed to the Streaming API is described in the Streaming API Concepts document: http://dev.twitter.com/pages/streaming_api_concepts It

Re: [twitter-dev] Streaming API vs. Search API: no API returns >95% of intented tweets

If you examine set C, do they contain matches on fields other than the Tweet text? To increase recall, search sometimes includes keywords in followed links and other techniques. Also, are you getting rate limit messages on the Streaming API? -John Kalucki http://twitter.com/jkalucki Twitter, Inc.

Re: [twitter-dev] Streaming API vs. Search API: no API returns >95% of intented tweets

I don't get that big a discrepancy, but I do get different results from search and streaming. I use streaming for real-time delivery, and then either search or user timelines to backfill missing tweets. As long as the flow makes this possible within rate limits this gets me the greatest number of r

Re: [twitter-dev] Streaming API setLocations Accuracy

$stream->setLocations(array( array(-87.60603635063173,41.78233280134992,-87.5898572658539,41.813078558257345) 2011-02-13 14:31:05 41.85087 , -87.69718 2011-02-13 13:14:07 41.85253 , -87.61243 2011-02-13 19:53:30 41.97302 , -87.90559 2011-02-13 19:35:11 41.97309 , -87.90595 2011-02-13 12:

Re: [twitter-dev] Streaming API setLocations Accuracy

Any exaples of tweets outside the box and the box itself? On Mon, Feb 14, 2011 at 6:59 PM, 1537 News <1537n...@gmail.com> wrote: > Good Afternoon > > I am using the StreamingAPI with a boundary box but finding it to be > inaccurate. > > I don't mind thinking outside the box :) but my a large % of

Re: [twitter-dev] Streaming API - Multiple connections on 1 IP?

Yes you can. On Thu, Dec 16, 2010 at 8:23 AM, epomqo wrote: > Hello everyone, > > Just a simple question: can I launch multiple connections to Streaming > API using different accounts, but on the same machine? The official > document seems don't say this clearly: > > "Each account may create onl

Re: [twitter-dev] Streaming API firehose visibility

Yes, where firehose is the stream of all public statuses, with some low-quality accounts removed. On Wed, Dec 1, 2010 at 3:52 PM, dburkes wrote: > If I am using the statuses/filter streaming API, with a "track=" query > that is not overly broad, and my client never receives any "limit" > respon

Re: [twitter-dev] Streaming API and OAuth

Streaming API doesn't differ from the REST API with it's authentication. Both use OAuth 1.0. Tom On 11/8/10 11:55 PM, Dewald Pretorius wrote: > Please update your documentation [1] for more detail information on > authenticating on the Streaming API with OAuth. > > We need to know the same type

Re: [twitter-dev] Streaming API and authentication

The streaming API supports basic auth *now*. At some point in the future it will not. If you're developing something new with basic auth you're setting yourself up for more work in the not too distant future. As far as the present message, only userstreams and sitestreams require oauth currently

Re: [twitter-dev] Streaming API, Basic Auth Ok, OAuth Unauthorized?

Hey Bradley, This is another instance of the the ongoing (and as yet un-answered sadly) question I have in the mailing list about my client (which iirc you're using) See : http://github.com/ciaranj/node-oauth/issues#issue/7 and http://groups.google.co.uk/group/twitter-development-talk/bro

Re: [twitter-dev] Streaming API question..

Hi Omri, Sorry, there's no option currently to filter by language. Taylor On Mon, Sep 27, 2010 at 1:50 AM, omri wrote: > hi there, > I am using the streaming API (the statuses/filter), and I get a lot of > tweets in spanish. > I wanted to know if there is a way to get results only in English?

Re: [twitter-dev] Streaming API skips users

Accounts should work all of the time, almost always with very low latency, unless they are protected accounts or otherwise filtered from search and streaming. Once an account is filtered, it should remain filtered for a very long time and not bounce back and forth. If you perform the same request

Re: [twitter-dev] Streaming API and oAuth

Yes, it does. Tom On Mon, 20 Sep 2010 06:16:03 -0700 (PDT), Joel Clinger wrote: > Hello, > > Does the streaming API still support Basic Auth? > Is there going to be any python module like tweepy that will support > oAuth and the streaming API? > > Thanks. > Joel -- Twitter developer documen

Re: [twitter-dev] Streaming API

You should use the Streaming API for large scale integrations. We're not doing much whitelisting for the REST API at the moment, but the shadow role on the Streaming API is generally available. If all of your users are public, use the shadow role on stream.twitter.com/1/statuses to get all of their

Re: [twitter-dev] Streaming API

1) Yes: the timelines are easier to use and more flexible, while the streaming API gives you realtime statuses and no problems with rate limits. 2) Streams. I'm not part of the Twitter team, but I really think that they would recommend Streams. Of course, it depends a bit on the situation. 3) I thi

Re: [twitter-dev] Streaming API limits

Hi Thiago, We allow each account to have one standing connection to the streaming API. Multiple connections receive the same stream of Tweets so connecting multiple times would not give access to any more Tweets. If you need more to have more track keywords you can contact us explaining your use c

Re: [twitter-dev] Streaming API limits

On 8/16/10 4:38 PM, Thiago Souza wrote: > Hi, > > I know that it's possible to track up to 200 keywords per account, > but how many accounts per IP is allowed? > > Regards, > Thiago Souza Hi Thiago, I don't think that Twitter will give you these numbers. Just don't create more connections t

Re: [twitter-dev] Streaming API (filter) and retweets, JSON Output

A retweet will have an embedded "retweeted_status" object. Example (first one from spritzer, not necessarily a favorite): { "coordinates": null, "favorited": false, "created_at": "Mon Aug 16 04:03:17 + 2010", "truncated": false, "retweeted_status": { "coordinates": null, "fa

Re: [twitter-dev] Streaming API and lists

Hi Thiago, The streaming API allows you to follow user IDs and track keywords but not lists directly. Instead you need to follow all the user IDs of the list and then assemble their Tweets on your server to recreate the list. Hope that helps, Matt On Thu, Aug 12, 2010 at 8:39 AM, thiago wrote:

Re: [twitter-dev] Streaming API and lists

If everyone on the list is public, you can fetch the user ids via REST, then use follow. Protected accounts won't show, of course. Also, on User Streams, you cannot specify your follow list. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, Aug 12, 2010 at 8:39 AM, thiago wrote:

Re: [twitter-dev] Streaming API for lists

We were planning to do lists, but we postponed the feature to get the bulk of User Streams to market sooner and to also get User Streams out to more users. We'll consider lists as an add-on later. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Jul 30, 2010 at 4:1

Re: [twitter-dev] Streaming API time drifting problem and possible solutions

Larry, moreover, I assume you checked I/O and CPU load. But even if that's not the issue, you should absolutely check if you have simplejson with c extension installed. The python included version is 1.9 which is decidedly slower than the new 2.x branch. You might see json decoding load drop by

Re: [twitter-dev] Streaming API time drifting problem and possible solutions

Larry, have you decoupled the processing code from tweepy's StreamListener, for example using a Queue.Queue oder some message queue server? Pascal On Jul 8, 2010, at 17:31 , Larry Zhang wrote: > Hi everyone, > > I have a program calling the statuses/sample method of a garden hose > of the Str

Re: [twitter-dev] Streaming API time drifting problem and possible solutions

Absolutely do not reset the connection and reconnect. Connections should be long-lived on the Streaming API. This is almost certainly a problem with the read throughput of your client, or, less likely, with bandwidth from your system. Run curl(1) from the same system and grep for the date field. I

Re: [twitter-dev] Streaming API and Oauth

Quoting John Kalucki: > We haven't announced our plans for streaming and oAuth, beyond stating that > User Streams will only be on oAuth. Right now, basic auth and oAuth both work on streaming, and that won't change when basic for REST turns off. Since there's no set shutdown date yet for bas

Re: [twitter-dev] streaming api - track - whitelisting for 10,000 keywords

Thanks Taylor and John. On Fri, Jul 2, 2010 at 7:03 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Hi Peter, > > First, make sure that you've used this form acquire garden hose > access: https://twitter.com/help/request_streaming > > Second, send an email to a...@twitter.com from

Re: [twitter-dev] streaming api - track - whitelisting for 10,000 keywords

Hi Peter, First, make sure that you've used this form acquire garden hose access: https://twitter.com/help/request_streaming Second, send an email to a...@twitter.com from the email address associated with the same Twitter account you filled that form out with, requesting "Track Restricted" strea

Re: [twitter-dev] Streaming API: Why not Curl?

It's not libcurl, per se, that's the problem, but just using curl(1) from a shell script doesn't necessarily give you the control that you might desire to build a stable client. You may want to set a connect timeout, socket timeout, perform parsing before persisting to disk, use overlapping connect

Re: [twitter-dev] Streaming API OAuth

Hi Jumpa, OAuth isn't supported for the Streaming API yet. We'll let everyone know the appropriate new access methods when they're fully baked. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, Apr 26, 2010 at 3:17 AM, Jumpa wrote: > Can I somehow use the OAuth i

Re: [twitter-dev] Streaming API

The curl man page explains how to send multiple parameters. If you just put them in one file, curl runs then all together. You have to separate them with &, or have curl do it for you by specifying multiple -d @ pairs: adrift.local:/tmp> head foo bar ==> foo <== follow=1234 ==> bar <== track=nort

Re: [twitter-dev] Streaming API OAuth explanation?

In the current incarnation, you don't need a registered application to use the streaming API -- just a valid username and password to access the endpoints. While we don't know what the OAuth-based authentication is going to look like in the future of authenticating with the streaming API, we do kn

Re: [twitter-dev] Streaming API OAuth explanation?

Hi, Question about oauth registration ... do I register the user ID I currently use at the same place as all other apps, i.e.http://dev.twitter.com/apps/new, or is there another endpoint for the streaming api? Thanks! ttyl Dima On Tue, Apr 20, 2010 at 10:17 AM, Taylor Singletary < taylorsinglet.

Re: [twitter-dev] Streaming API OAuth explanation?

Hi Jonathon, For Streaming API access that isn't from the perspective of a user's account, you would use two-legged OAuth to establish authentication instead of basic auth. A two-legged OAuth request is very similar to other OAuth requests: you have a specific resource you are trying to access, y

Re: [twitter-dev] Streaming API not returning any data

The Streaming API is currently configured to send a keep-alive newline every 30 seconds. If you don't receive any data or the keep-alive in perhaps 60 or 90 seconds, you should drop and reconnect. The only case where what you observed should happen is if a load balancer restarts. I don't think this

Re: [twitter-dev] Streaming API track vs. Search results

Also ensure that your client is logging the raw data as received from the socket. Sometimes this will narrows an issue down to a parsing or similar error in the client. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 16, 2010 at 9:01 AM, Mark McBride wrote: >

Re: [twitter-dev] Streaming API track vs. Search results

If you can duplicate this, can you send the exact text, tweet IDs and times of the runs? Latency on the streaming API should be better than it is in search (they're both pretty fast), so having the streaming API lag search is surprising. ---Mark http://twitter.com/mccv On Fri, Apr 16, 2010 a

Re: [twitter-dev] Streaming API - weird data in JSON text

2010/4/14 Mad Euchre : > Can someone please tell me why some tweets have the following as the > text? > > "text":"\uc624\ub298 \uc2dc\uac00\ucd1d\uc561\uc774 $AAPL \uc740 > $208.0B \uc774\uace0 $GOOG \uc740 $177.2B \ub124\uc694. > \uadf8\ub3d9\uc548 \uc5c5\uce58\ub77d \ub4a4\uce58\ub77d\ud558\ub358

Re: [twitter-dev] Streaming API - weird data in JSON text

Unicode? http://json.org/ -josh 2010/4/14 Mad Euchre : > Can someone please tell me why some tweets have the following as the > text? > > "text":"\uc624\ub298 \uc2dc\uac00\ucd1d\uc561\uc774 $AAPL \uc740 > $208.0B \uc774\uace0 $GOOG \uc740 $177.2B \ub124\uc694. > \uadf8\ub3d9\uc548 \uc5c5\uce58

Re: [twitter-dev] Streaming API TOS

Both of those use cases are fine. The intent was to prevent people from publishing counts of Tweets per day or similar metrics. (I make no pretense at defending this intent, I'm the messenger.) Go forth and wordle. This EULA is near the end of its life and has been rewritten into the Commercial Da

Re: [twitter-dev] Streaming API with Chinese/Japanese language track predicates

There are people here at Twitter who know this stuff inside and out. I just haven't, yet, roped them in for a fix. Once we have a fix in hand, we'll publish recommendations for everyone. Whatever our streaming servers have to do, your streaming clients have to do, and we might as well pool our effo

Re: [twitter-dev] Streaming API with Chinese/Japanese language track predicates

- "John Kalucki" wrote: > We break the status text into tokens by whitespace and punctuation, > then apply the tokens to a hashmap of tracked terms. If the language > doesn't have whitespace, the only thing that will match is the entire > Tweet. > > I know that Search has struggled with thi

Re: [twitter-dev] Streaming API with Chinese/Japanese language track predicates

We break the status text into tokens by whitespace and punctuation, then apply the tokens to a hashmap of tracked terms. If the language doesn't have whitespace, the only thing that will match is the entire Tweet. I know that Search has struggled with this as well. I take it that the solutions are

Re: [twitter-dev] Streaming API -- filtering with punctuation

You really shouldn't pick your systems based on what Twitter uses unless all else is the same. Our requirements are radically different from yours. I'd encourage you to use the same libraries though -- for example, if we're using Gson to parse JSON, you are unlikely to run into additional complica

Re: [twitter-dev] Streaming API -- filtering with punctuation

On 03/26/2010 10:32 AM, John Kalucki wrote: > The combinatorics don't work out here until we offer boolean AND. Tokens are > thrown against a HashMap to determine delivery. It's not really feasible to > also throw arbitrary combinations of tokens against the HashMap. If we ever > support AND, then

Re: [twitter-dev] Streaming API -- filtering with punctuation

The combinatorics don't work out here until we offer boolean AND. Tokens are thrown against a HashMap to determine delivery. It's not really feasible to also throw arbitrary combinations of tokens against the HashMap. If we ever support AND, then you could search for ow AND ly. You'll have to over

Re: [twitter-dev] Streaming API , statuses/filter using track

The Streaming API only serves current statuses and a short history, controlled by the count parameter. Use one of the REST APIs to backfill. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 22, 2010 at 5:26 AM, Kislay wrote: > Hi , > > I would like to know whe

Re: [twitter-dev] streaming api

I'm not familiar with your library but by just looking at the snippet you see .For(10.Seconds()).Take(100) I'd imagine if instead of 10 seconds you'd pass 10 years and instead of 100 you'd pass something infinitely larger, you'd experience more of a stream? On Mar 20, 2010, at 3:01 AM, riz

Re: [twitter-dev] streaming api

Perhaps the 10.Seconds() and Take(100) functions are limiting your output? It seems that this framework is perhaps not streaming, but assuming a finite response size? I'd ask on the TweetSharp dev list. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sat, Mar 20, 2010 a

Re: [twitter-dev] Streaming API Basic Auth

Would JSONP be a fit for your situation? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Mon, Mar 15, 2010 at 8:06 PM, Lawrence wrote: > Hi Everyone, > I am developing a Twitter

Re: [twitter-dev] Streaming API (filtered) missing Tweets

Do those same users show in search? If not, chances are that those users are filtered for quality from both Search and Streaming. If the users do show in Search, there's probably something wrong with your filter predicates. Note that track only searches on status text, not on the entire status obj

Re: [twitter-dev] Streaming API Basic Auth

We do indeed have crossdomain.xml disabled on stream.twitter.com. If that's required, you'll have to wait a bit before deploying a Javascript solution. If that isn't the problem, I'd suggest using tcpdump or some other wire inspection tool and see what is transpiring directly. The Streaming API of

Re: [twitter-dev] Streaming API JSON Decode Double Errors?

We can't answer your question for you since we have no idea what you're receiving. What does the streaming response look like that your consumer is tripping over? Capture it in association with log events. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [

Re: [twitter-dev] Streaming API follow limit

Documented here: http://apiwiki.twitter.com/Streaming-API-Documentation#statuses/filter To get access to the higher limit roles, you'll need to contact a...@twitter.com. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 3:11 PM, Lucas Vickers wrote:

Re: [twitter-dev] Streaming API Best Practice (Multiple Connections or Single)

The documentation should be pretty clear on this topic. One main connection, and perhaps an auxiliary connection to manage query velocity. You must not proliferate connections to work around rate limits. Instead, you must apply for higher access. Connections are expensive. http://apiwiki.twitter.c

Re: [twitter-dev] Streaming API connection abandonment & separation anxiety issues

connection issue around 15:56 UTC, see our log below: 22-02-2010 16:55:41 - Consume rate: 13 status/sec (764 total), avg enqueueStatus(): 1.51ms, avg checkFilterPredicates(): 349.46ms (12 total) over 60 seconds. 22-02-2010 16:56:18 - Phirehose connection error occured: 22-02-2010 16:56:18 - Closin

Re: [twitter-dev] Streaming API connection abandonment & separation anxiety issues

* John Kalucki [100222 10:51]: > If you had a correlative experience within a minute or so of 15:55 UTC, > please respond to this message. Indeed, I did. From the application log: 2010/02/22 07:56:14 9481340618: RT @whitehouse: The Presi... 2010/02/22 07:57:14 timeout 2010/02/22 07:57:14 Waitin

Re: [twitter-dev] Streaming API question

60 or 90 seconds seems reasonable, but your code should also detect a socket close immediately and reconnect immediately. The common case for a connection drop -- a server restart -- should cause your socket to close, the client to detect the closure, and reconnect, all within about a second. On

Re: [twitter-dev] Streaming API question

* John Kalucki [100220 21:02]: > Arg. This is what I get for not checking the configuration each time. Yes, > it's currently set to send a newline every 30 seconds. Ok. Sorry to drag this out, but what, then, is an appropriate timeout value for the application? @semifor

Re: [twitter-dev] Streaming API question

Arg. This is what I get for not checking the configuration each time. Yes, it's currently set to send a newline every 30 seconds. On Sat, Feb 20, 2010 at 8:45 PM, Marc Mims wrote: > * John Kalucki [100220 20:24]: > > A 45 second period of inactivity is not unusual when following just 100, > o

Re: [twitter-dev] Streaming API question

* John Kalucki [100220 20:24]: > A 45 second period of inactivity is not unusual when following just 100, or > even 100,000 users. The keep-alive newlines are only sent once every 10 > minutes. You should not reconnect so aggressively. I can certainly set the time out to 10 minutes. I'm seeing n

Re: [twitter-dev] Streaming API question

A 45 second period of inactivity is not unusual when following just 100, or even 100,000 users. The keep-alive newlines are only sent once every 10 minutes. You should not reconnect so aggressively. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sat, Feb 20, 2010 at 7

Re: [twitter-dev] Streaming API question

* rob [100219 08:56]: > Has anyone else ran into an issue where over time the Streaming API > just stops sending results? Yes. I'm seeing the same thing. I've set up a 45 second timeout. The following entries were extracted from the application log. I'm currently following < 100 users, so perio

Re: [twitter-dev] Streaming API question

This shouldn't be happening, and having developers build these sorts of workarounds saddens me. It is possible that the server side is holding dead connections open, but I doubt it -- as I've a considerable amount of data to the contrary. I suspect that the socket code does not detect a close, dri

Re: [twitter-dev] Streaming API question

Hi, Yup, I saw it the last couple of weeks, this week has been considerably better. I use the delimited stream so I do read(entry size), read(entry), repeat ... I just put a 30 second timeout on the read operation (this is all in python) and if a read fails I close the stream and reconne

Re: [twitter-dev] Streaming API question

Me too! Exact same case. I am using tweepy. On Fri, Feb 19, 2010 at 10:36 AM, rob wrote: > Has anyone else ran into an issue where over time the Streaming API > just stops sending results? > > We are using a Ruby library to connect (twitter-stream) which uses > EventMachine to open a persistent

Re: [twitter-dev] Streaming API and older tweets?

Thank you for your very complete answer John. That is exactly what I was thinking. From what I can tell my tag isn't very high traffic so I'm going to go check the search API to pull the older results and leave my current Streaming client running to pull anything new. Thank you! On Fri, Jan 22,

Re: [twitter-dev] Streaming API and older tweets?

You can use the Search API to do historical queries when you first start following a hash tag, then switch to Streaming. Search results may be incomplete but sufficient in this case. Currently the count parameter is not supported in conjunction with track on any role, due to both cost and scraping

Re: [twitter-dev] streaming api results?

I'll update the doc. The best place to look right now is here http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses show, which has a sample status return. ---Mark http://twitter.com/mccv On Tue, Jan 19, 2010 at 7:25 AM, joelkeepup wrote: > Hi, > > Hi, reading documentation at: > ht

Re: [twitter-dev] Streaming API - Partial word match

In the short term there are no plans to support partial matching. It's considerably more expensive than the current implementation. ---Mark http://twitter.com/mccv On Mon, Jan 18, 2010 at 1:05 PM, vivekpuri wrote: > Search API team is recommending developers to migrate over to > Streaming

Re: [twitter-dev] Streaming API Basics ...

1) The sample resource returns a sampled stream, best for statistical analysis and the like. The filtered resource returns a stream filtered by the supplied predicates. You will mostly be using the filtered resource. 2) Retweets can be found with the follow parameter. See http://apiwiki.twitter.co

Re: [twitter-dev] Streaming API - Partial word match

I've been able to track act.ly urls by using "act". So try "bit" and just throw out anything that isn't a bit.ly url. On Mon, Jan 18, 2010 at 1:05 PM, vivekpuri wrote: > Search API team is recommending developers to migrate over to > Streaming API. To get started with this, i was looking at the

Re: [twitter-dev] Streaming API tweets delayed by ~20 minutes

We have extensive monitoring on all streams and graph the worst case latency for every server in several ways, from several locations. If latency increases just slightly, alarms go off. I think you must be looking at something else. Try this: In one window: curl -s stream.twitter.com/1/statuses/

Re: [twitter-dev] Streaming API - AND between filter keywords

Currently no. What I would do is search for "Francisco" (a much rarer term), and then manually check for "San Francisco" on your end. ---Mark http://twitter.com/mccv On Sat, Jan 9, 2010 at 2:32 PM, Amitab wrote: > Hi folks, > > Is there a way by which I can get streaming results tracking

Re: [twitter-dev] Streaming API

All Twitter accounts have access to the Spritzer access level on /1/statues/sample.format. The Gardenhose rate increases the flow on that same resource by about three times. You have to agree to a EULA. Email a...@twitter.com to get started. -John Kalucki http://twitter.com/jkalucki Services, Twit

  1   2   >