I understand the APIs from a technical perspective. The issue is about twitter 
*policy* around rate limits and connection limits. As a non whitelisted app we 
will quickly run into rate limits so I am just trying to understand what the 
current rules are.

On Mar 2, 2011, at 10:52 AM, Adam Green <140...@gmail.com> wrote:

> There are lots of ways to create website apps without using site
> streams. If you describe the type of things you want to do here, you
> will get plenty of advice. You don't have to reveal any secret plans.
> Just describe the type of data you need from Twitter and the type of
> changes you need to make to user accounts.
> 
> On Wed, Mar 2, 2011 at 10:37 AM, hank777 <hank...@gmail.com> wrote:
>> I just registered for site streams this morning because I did not
>> realize that this was the only authorized way of building a website
>> that uses twitter. We are trying to demo something at SXSW, and launch
>> a few weeks after, and I am wondering if I cant use the other APIs
>> because of rate limits or connection limits, and I cant use site
>> streams because you are not accepting new developers, how do we move
>> forward, or does this really mean no one should be developing new web
>> site based applications right now if they are not in the beta program?
>> 
>> Thanks,
>> Hank
>> 
>> On Feb 1, 10:36 am, Taylor Singletary <taylorsinglet...@twitter.com>
>> wrote:
>>> We still have a number of tasks to accomplish before we can move to the next
>>> stage of the beta. Pending applications will be reviewed once they are
>>> actionable.
>>> 
>>> Thanks for your patience.
>>> 
>>> Taylor
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, Jan 31, 2011 at 7:20 PM, Jan Paricka <jpari...@gmail.com> wrote:
>>>> Weeks upon weeks upon weeks.  No joking.
>>> 
>>>> Jan
>>> 
>>>> On Tue, Feb 1, 2011 at 4:14 AM, paloalto <sungh...@gmail.com> wrote:
>>> 
>>>>> How long does it take to get whitelisted for Site Streams API?
>>>>> I submitted a form to be whitelisted and have not received any
>>>>> confirmation e-mail.
>>>>> I am in the dark with no clue as to how long I should expect to wait.
>>> 
>>>>> Sungho
>>> 
>>>>> --
>>>>> 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
>> 
> 
> 
> 
> -- 
> Adam Green
> Twitter API Consultant and Trainer
> http://140dev.com
> @140dev
> 
> -- 
> 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

Reply via email to