I'm still waiting too.
Put the request in on 28th Feb. Got a response to sign ToS just under
3 weeks later. Responded immediately, been waiting over 2 weeks for a
response to that.
HTH,
dw.
On Mar 2, 5:12 pm, Rich <
rhyl...@gmail.com> wrote:
> I'm still waiting. I did get an email on the 21st Feb asking me to
> sign a ToS forSiteStreamsand reply... which I duly did a few
> minutes later.
>
> Yet I've heard nothing since then. Someone at Twitter did reply to me
> on Twitter itself saying they are usually reviewed every 1 to 2 weeks,
> but again nothing since then.
>
> On Mar 2, 4:09 pm, Hank Williams <
hank...@gmail.com> wrote:
>
> > 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 usingsite
> > >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 forsitestreamsthis 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 usesite
> > >>streamsbecause you are not accepting new developers, how do we move
> > >> forward, or does this really mean no one should be developing new web
> > >>sitebased applications right now if they are not in the beta program?