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 but keep receiving 413 response errors. Kind of weird. J On Thu, Feb 24, 2011 at 5:52 AM, Matt Harris thematthar...@twitter.comwrote: 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 says: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. When tracking users using the Streaming API the default level allows 5000 follower IDs to be tracked. Make sure the user_ids are specified with the follow parameter and not the track parameter. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote: Hi, Just started to play with streaming API, but get confused on how many followers id could be tracked with one connection. In basic level of filter, http://dev.twitter.com/doc/post/statuses/filter says 400 followers ids http://dev.twitter.com/pages/streaming_api_methods says 5,000 followers ids Then I tried in local machine, could only follow around 320 ids ( receive 413 if more) and seems multiple connections in one IP are not allowed. Any body here know: Is there any ways to follow a few thousands ids for each authenticated account (with oauth)? Or how to apply for higher access level? Any experience share or answers are appreciated! J -- 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
[twitter-dev] There's a bug with dev.twitter.com
Hi... I'm slowly making my way through the OAuth landscape of twitter and I ran into a very odd inconsistency. I registered my application and kept getting 401 HTTP errors (Unauthorized) using the Ruby OAuth library. If I access my application details via: http://dev.twitter.com/apps/edit/12341234 Compared with accessing it via: http://twitter.com/apps/edit/12341234 There's one checkbox that doesn't appear on the dev version: Yes, use Twitter for login After checking this, I was then able to get OAuth going. Is this deliberate? Or just an omission? Is this a sign that the Twitter API is going to prevent logins? How does that work with OAuth then? Cheers, Jason -- 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-dev] Apps that Site Hack
Spam applications like Tweetadder, TheTweetTank and many others like it are currently hacking the website to get round oauth and basic auth restrictions - what is Twitter doing to level the playing field for serious developers who use oauth and follow Twitter guidelines? Many thanks in advance, Alan Hamlyn MarketMeSuite -- 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-dev] Re: Streaming API access level limit
Hello Matt. Could you tell me (us) what the limit is on track parameter? Thank you in advance. Regards. Alejandro. On Feb 23, 6:52 pm, Matt Harris thematthar...@twitter.com wrote: 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 says: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. When tracking users using the Streaming API the default level allows 5000 follower IDs to be tracked. Make sure the user_ids are specified with the follow parameter and not the track parameter. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote: Hi, Just started to play with streaming API, but get confused on how many followers id could be tracked with one connection. In basic level of filter, http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids http://dev.twitter.com/pages/streaming_api_methodssays 5,000 followers ids Then I tried in local machine, could only follow around 320 ids ( receive 413 if more) and seems multiple connections in one IP are not allowed. Any body here know: Is there any ways to follow a few thousands ids for each authenticated account (with oauth)? Or how to apply for higher access level? Any experience share or answers are appreciated! J -- 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
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 likely contain the clues as to what's going wrong. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 24, 2011 at 1:34 AM, 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. J On Thu, Feb 24, 2011 at 5:52 AM, Matt Harris thematthar...@twitter.comwrote: 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 says: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. When tracking users using the Streaming API the default level allows 5000 follower IDs to be tracked. Make sure the user_ids are specified with the follow parameter and not the track parameter. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote: Hi, Just started to play with streaming API, but get confused on how many followers id could be tracked with one connection. In basic level of filter, http://dev.twitter.com/doc/post/statuses/filter says 400 followers ids http://dev.twitter.com/pages/streaming_api_methods says 5,000 followers ids Then I tried in local machine, could only follow around 320 ids ( receive 413 if more) and seems multiple connections in one IP are not allowed. Any body here know: Is there any ways to follow a few thousands ids for each authenticated account (with oauth)? Or how to apply for higher access level? Any experience share or answers are appreciated! J -- 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 -- 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
Re: [twitter-dev] Re: Streaming API access level limit
Alejandro, You can track up to 400 keywords/terms at the basic level, with each term up to 60 bytes. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 24, 2011 at 5:46 AM, AA alejandro.ale...@gmail.com wrote: Hello Matt. Could you tell me (us) what the limit is on track parameter? Thank you in advance. Regards. Alejandro. On Feb 23, 6:52 pm, Matt Harris thematthar...@twitter.com wrote: 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 says: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. When tracking users using the Streaming API the default level allows 5000 follower IDs to be tracked. Make sure the user_ids are specified with the follow parameter and not the track parameter. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote: Hi, Just started to play with streaming API, but get confused on how many followers id could be tracked with one connection. In basic level of filter, http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids http://dev.twitter.com/pages/streaming_api_methodssays 5,000 followers ids Then I tried in local machine, could only follow around 320 ids ( receive 413 if more) and seems multiple connections in one IP are not allowed. Any body here know: Is there any ways to follow a few thousands ids for each authenticated account (with oauth)? Or how to apply for higher access level? Any experience share or answers are appreciated! J -- 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 -- 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-dev] Re: should search and streaming apis return similar tweets for equivalent geolocation areas
Did not receive any answer on the questions below. I think it is important for us developers to understand the direction Twitter is taking in relation to geolocalized searches. In a nutshell: For geolocalized searches, the streaming API returns a very small fraction (3% in my tests) of what the search API returns. This is because the streaming API only uses the geotagging API to locate tweets, but the search API uses both the geotagging API and the user location field. Depending on your application, both methods can be valuable. In particular, what the search API retrieves make sense in my context but it is not possible to get this using the streaming API. - Can we expect both methods to be supported in the future and can we expect to get a streaming version of what the search API does today? Thanks, Colin On Feb 15, 2:19 pm, Colin Surprenant colin.surpren...@gmail.com wrote: So basically today we have two options for geo search: - use the search api and get results that will include some incorrectly geolocalized tweets when falling back on the user location field. - use the streaming api and retrieve significantly far less tweets but with a higher degree of confidence in their geolocation using only the geotagging api. Can we expect these two methods to be available concurrently for the next 3, 6, 12 months? I have two problems with this: - As developers we are asked to migrate toward the streaming api instead of using periodic polling, which makes sense. But for geo search, the streaming api is not a viable alternative for those who actually prefer/require/want the behaviour of the geo search api. - The fact the the streaming api returns far less but more precise data is not necessarily better, it really depends who you ask. For me, having lots of geolocalized data that will contain a fraction of invalid data is far more valuable than having far less but more accurate data. My tests told me the streaming api currently returns only ~3% of the volume of data the search api produces. If the only difference between the search api and the streaming api is the usage of the user location field, then we can certainly say that FAR more people are still only using their user location field and not using the geotagging api. Will you offer an option in the streaming api to fall back or not on the user location field when evaluating the geolocation of a tweet? Thanks, Colin On Feb 14, 2:33 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Colin, You hit the nail on the head with this observation: In the doc it says that the streaming API will only return tweets that are created using the Geotagging API (and within the bounding box) but the search API will preferentially use the Geotagging API, but will fall back to the Twitter profile location. The Search API is greedy with those location fields on user's profiles. It's not likely this behavior will be emulated in the Streaming API with the bright side that you can be more confident in the location accuracy in matches on the Streaming API. Thanks, Taylor -- 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-dev] signup API
Is it possible to signup to Twitter using some kind of signup API? I looked, and didn't see anything. Thanks -- 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-dev] Seeing many Woah there errors on oauth/authenticate
Our users are reporting many sporadic Woah there errors on the oauth/ authenticate page, where the error says the token info was already used. We're forwarding our users to that page immediately after we get the token info. Is this a problem with our oauth logic (we're using Twitter Async / EpiTwitter) or is it an API issue? Thanks, Aaron -- 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
Re: [twitter-dev] signup API
There is no public API for this at the moment. Sent from my iPhone On 24 Feb 2011, at 17:34, Anil replic...@gmail.com wrote: Is it possible to signup to Twitter using some kind of signup API? I looked, and didn't see anything. Thanks -- 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
[twitter-dev] Re: Intermittent 401 errors calling access_token
On Feb 10, 8:40 am, Peter Motyka pmot...@gmail.com wrote: I'm seeing intermittent issues as well on the /oauth/access_token endpoint. Have you ever gotten to the bottom of this or is it just best to handle the error and retry? Below is a capture of my HTTP requests: No resolution on this issue. I've collected details on the full chain of calls for about 100 of these failures, now. They seem to be occurring more frequently (although, that may be the result of more application use rather than a higher failure rate). Retrying the access_token call does not seem to be sufficient (that always fails, in my experience); it's necessary to start the process over with oauth/authorize (or oauth/authenticate). If Twitter is interested in the details, I'd be happy to supply them. -Marc -- 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
Re: [twitter-dev] Seeing many Woah there errors on oauth/authenticate
On Thu, 24 Feb 2011 09:41:34 -0800 (PST), Aaron Rankin aran...@sproutsocial.com wrote: Our users are reporting many sporadic Woah there errors on the oauth/ authenticate page, where the error says the token info was already used. We're forwarding our users to that page immediately after we get the token info. Is this a problem with our oauth logic (we're using Twitter Async / EpiTwitter) or is it an API issue? Thanks, Aaron As a user, I've seen a fair number of those from some applications too. I just saw one from PeerIndex, in fact. I ended up having to revoke access and sign out of Twitter, then sign back in. I'm guessing this isn't on Twitter's end. Could this be some kind of clock mismatch between the application and Twitter? -- 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
Re: [twitter-dev] Streaming API access level limit
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
Re: [twitter-dev] Seeing many Woah there errors on oauth/authenticate
Fairly sure this is on our end and it's a flavor of cache-sync issue. The issue has been raised with engineering and we hope to have it fixed soon. A page refresh on the woah there page seems to help for some people. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 24, 2011 at 10:01 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 24 Feb 2011 09:41:34 -0800 (PST), Aaron Rankin aran...@sproutsocial.com wrote: Our users are reporting many sporadic Woah there errors on the oauth/ authenticate page, where the error says the token info was already used. We're forwarding our users to that page immediately after we get the token info. Is this a problem with our oauth logic (we're using Twitter Async / EpiTwitter) or is it an API issue? Thanks, Aaron As a user, I've seen a fair number of those from some applications too. I just saw one from PeerIndex, in fact. I ended up having to revoke access and sign out of Twitter, then sign back in. I'm guessing this isn't on Twitter's end. Could this be some kind of clock mismatch between the application and Twitter? -- 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
[twitter-dev] current response issues at Twitter.com?
Is something happening? I'm seeing Loading Tweets seems to be taking a while. Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information. pretty regularly at the moment. Search, on the other hand, seems to be fine. -- 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-dev] Streaming API limits...
Now that I've got OAuth with statuses/follow.json working, I've been working through building a small part of our app. Part of the streaming API docs state that only one connection is allowed (reasonable). Upon making a second connection, the first no longer receives any data (not even anti-timeout newlines), nor does it get connected by the server. On my end of things, I've written an async client which can detect such a condition (it watches a shared Redis key looking for a changed state when it doesn't receive any data for a while), and automatically disconnects. The streaming API docs also state that repeated reconnections, etc., are frowned upon and may result in banning. My question is simple: how often can I reconnect to follow different people/keywords? Obviously ten times a second is well beyond reasonable and would probably get us banned in seconds. But isat most once every 5 minutes okay? At most once every minute? At what level would we be safe? Thank you, - Josiah -- 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-dev] Re: Apps that Site Hack
Apart from implementing reCAPTCHA on tweet submission, follow, and unfollow, I can't see what Twitter can do to prevent that kind of abuse (can you imagine the revolt by bona fide users?). How else do you determine that it is an actual human and not a piece of automated software behind the browser on the user's desktop or laptop? The only other option is legally, and that depends on the country of residence of the owners of the software. At this point in time, it appears that anyone who is able to and have the inclination to write desktop software that bypasses the API might have carte blanche to do so. On Feb 24, 7:00 am, Alan Hamlyn alanhamlyn...@gmail.com wrote: Spam applications like Tweetadder, TheTweetTank and many others like it are currently hacking the website to get round oauth and basic auth restrictions - what is Twitter doing to level the playing field for serious developers who use oauth and follow Twitter guidelines? Many thanks in advance, Alan Hamlyn MarketMeSuite -- 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
Re: [twitter-dev] Re: Streaming API access level limit
Taylor: Thanks for your answer! Is it possible to be allowed to track more keyword/terms than 400? How can I do it? Thank you in advance. Regards. Alejandro. 2011/2/24 Taylor Singletary taylorsinglet...@twitter.com Alejandro, You can track up to 400 keywords/terms at the basic level, with each term up to 60 bytes. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 24, 2011 at 5:46 AM, AA alejandro.ale...@gmail.com wrote: Hello Matt. Could you tell me (us) what the limit is on track parameter? Thank you in advance. Regards. Alejandro. On Feb 23, 6:52 pm, Matt Harris thematthar...@twitter.com wrote: 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 says: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. When tracking users using the Streaming API the default level allows 5000 follower IDs to be tracked. Make sure the user_ids are specified with the follow parameter and not the track parameter. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote: Hi, Just started to play with streaming API, but get confused on how many followers id could be tracked with one connection. In basic level of filter, http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids http://dev.twitter.com/pages/streaming_api_methodssays 5,000 followers ids Then I tried in local machine, could only follow around 320 ids ( receive 413 if more) and seems multiple connections in one IP are not allowed. Any body here know: Is there any ways to follow a few thousands ids for each authenticated account (with oauth)? Or how to apply for higher access level? Any experience share or answers are appreciated! J -- 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 -- 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-dev] tweet data set
I am looking for a tweet data set, with at least 100M tweets in it. It is fine if this data is anonymized, and if the users are anonymized as well. I am using this to train a machine learning classifier. If anyone knows of such a collection, can you let me know where I can gain access to it? Thanks. -- 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-dev] Random empty results from statuses/user_timeline ?
I have a twitter app on iOS that loads a user profile, then their list of friends then tweets from a handful of the friends. During this last part I'm using a API call like: https://api.twitter.com/1/statuses/user_timeline/akmed13.json?include_entities=truetrim_user=truepage=4count=50 The problem I'm noticing is that sometimes this returns an empty collection. The app logs the call as suspicious since it didn't generate an error but was also an empty result, I then try the call in my browser and it always works as expected (I get the list of tweets in json). Is there anything I can do to help prevent this behavior. Its very sporadic best I can tell. I'm stumped. I've tried googling but am not seeing anything. I don't think it's a rate limit issue as I'm not getting back error codes, and later queries work fine. I don't think its a capacity issue as I've seen those, they come back as 502. Any suggestion welcome. Thanks. ~ Mike -- Michael Zornek Clickable Bliss http://clickablebliss.com/ -- 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
