wait time for Site Streams whitelist ?

27 views
Skip to first unread message

paloalto

unread,
Jan 31, 2011, 10:14:22 PM1/31/11
to Twitter Development Talk
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

Jan Paricka

unread,
Jan 31, 2011, 10:20:15 PM1/31/11
to twitter-deve...@googlegroups.com
Weeks upon weeks upon weeks.  No joking.

Jan



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

Taylor Singletary

unread,
Feb 1, 2011, 10:36:36 AM2/1/11
to twitter-deve...@googlegroups.com
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

hank777

unread,
Mar 2, 2011, 10:37:45 AM3/2/11
to Twitter Development Talk
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
>

Adam Green

unread,
Mar 2, 2011, 10:52:28 AM3/2/11
to twitter-deve...@googlegroups.com
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.

--
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

Hank Williams

unread,
Mar 2, 2011, 11:09:35 AM3/2/11
to twitter-deve...@googlegroups.com, twitter-deve...@googlegroups.com
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.

Rich

unread,
Mar 2, 2011, 11:12:11 AM3/2/11
to Twitter Development Talk
I'm still waiting. I did get an email on the 21st Feb asking me to
sign a ToS for Site Streams and 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 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.
>

David W

unread,
Apr 5, 2011, 7:02:10 AM4/5/11
to Twitter Development Talk
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?

Nicholas Chase

unread,
Apr 5, 2011, 7:46:34 AM4/5/11
to twitter-deve...@googlegroups.com
I put in my request on 2/21 and got approved on 3/3. I should point
out, though, that I did email (just once!) to follow up.

---- Nick

Mark Krieger

unread,
Apr 6, 2011, 10:01:49 AM4/6/11
to Twitter Development Talk
Taylor,

Can you give us some time estimate? I have a development team stuck
now, nothing more we can do to test with User Streams. I put in weeks
ago too for this whitelisting.

Mark

Taylor Singletary

unread,
Apr 6, 2011, 10:15:07 AM4/6/11
to twitter-deve...@googlegroups.com, Mark Krieger
Hi all,

Site Streams is still in beta and the wait times are variable based on the needs & constraints of the beta program. As with any beta, we're learning what more is necessary to productionize the API at scale to the kinds of applications that are requesting access -- by requesting access, you're not only making that request, you're giving us information about the types of scenarios, user profiles, and growth rates that you project -- all data that we need to properly scale the system so that we can release it with confidence.

Thanks,
Taylor

David W

unread,
Apr 7, 2011, 8:02:22 AM4/7/11
to Twitter Development Talk
Hey Taylor,
Thanks for the response, totally appreciate that Site Streams is in
beta and as such wait times and access may vary.

It would help us a lot if we could however get some more feedback on
our beta application, even if it's to say "we're not giving you access
yet because xyz - we'll re-review your application in x weeks".

As Mark said, getting no feedback makes it very hard to plan. We're
kinda in limbo - we can't apply for whitelist access and we don't have
Site Streams access and have no idea if we ever will.

Thanks,
dw.

On Apr 6, 3:15 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Hi all,
>
> Site Streams is still in beta and the wait times are variable based on the
> needs & constraints of the beta program. As with any beta, we're learning
> what more is necessary to productionize the API at scale to the kinds of
> applications that are requesting access -- by requesting access, you're not
> only making that request, you're giving us information about the types of
> scenarios, user profiles, and growth rates that you project -- all data that
> we need to properly scale the system so that we can release it with
> confidence.
>
> Thanks,
> Taylor
>

David W

unread,
Apr 18, 2011, 8:10:29 AM4/18/11
to Twitter Development Talk
I'm intrigued - has anyone else been given Site Streams access in the
last month? We signed the Terms of Service over a month ago and have
heard nothing since, despite asking here, via email and via
@SiteStreams

I'm interested to know whether all applications have been frozen or
whether it's just ours for unknown reasons.

Thanks,
dw.

Mamadou Bobo Diallo

unread,
Apr 18, 2011, 7:39:53 PM4/18/11
to Twitter Development Talk
We are all waiting for Site Stream whitelisting. The issues here is
that you are stuck not knowing either you should invest more time in
building a product "you never tested". Unfortunatly, site stream is
the only API on which our product make sense building on.

So let have finger crossed and hope we'll get one day an email from
twitter.

David W

unread,
Apr 19, 2011, 3:34:52 AM4/19/11
to Twitter Development Talk
Well it's taken 7 weeks, but I finally got an email basically saying
we weren't accepted onto the beta program.

Fair enough - it is a beta, least we can make other plans now.

dw.
Reply all
Reply to author
Forward
0 new messages