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

2011-02-28 Thread Chen Jack S Y
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 j...@twitter.com wrote:

 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 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


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

2011-02-28 Thread Matt Harris
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,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Mon, Feb 28, 2011 at 12:54 AM, Chen Jack S Y aquaj...@gmail.com wrote:

 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 j...@twitter.com wrote:

 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 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] Streaming API access level limit

2011-02-28 Thread Augusto Santos
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 thematthar...@twitter.comwrote:

 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,
  @themattharris
 Developer Advocate, Twitter
 http://twitter.com/themattharris


 On Mon, Feb 28, 2011 at 12:54 AM, Chen Jack S Y aquaj...@gmail.comwrote:

 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 j...@twitter.com wrote:

 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 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




-- 
氣

-- 
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

2011-02-28 Thread Chen Jack S Y
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 thematthar...@twitter.com wrote:

 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,
 @themattharris
 Developer Advocate, Twitter
 http://twitter.com/themattharris


 On Mon, Feb 28, 2011 at 12:54 AM, Chen Jack S Y aquaj...@gmail.com wrote:

 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 j...@twitter.com wrote:

 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 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

-- 
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

2011-02-27 Thread John Kalucki
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 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


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

2011-02-25 Thread Chen Jack S Y
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


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

2011-02-24 Thread Chen Jack S Y
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


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

2011-02-24 Thread Taylor Singletary
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] Streaming API access level limit

2011-02-24 Thread M. Edward (Ed) Borasky
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] Streaming API access level limit

2011-02-23 Thread Matt Harris
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