"won't sustain more than 15 users"
Why not? If you have 15 users, you can spread the API calls over them
and the last time I checked, 15*350 gives you 5250 API calls.
Tom
On 2/12/11 7:24 PM, Jan Paricka wrote:
Cool. I am weeks from launch and I am fucked. Without whitelisting, my
app won't sustain more than 15 users. Thank you twitter, thank you very
much. Btw, I really hoped to launch at @geekn'rolla
Jan
On Sat, Feb 12, 2011 at 6:33 PM, mabujo <jaa...@gmail.com
<mailto:jaa...@gmail.com>> wrote:
Jan, yes twitter have said they're removing whitelisting for new
requests, see here :
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84
On Feb 12, 5:37 pm, Jan Paricka <jpari...@gmail.com
<mailto:jpari...@gmail.com>> wrote:
> Whoa, does that mean twitter is no longer whitelisting??
>
> Guys, I spent nearly two years working on the app - it's nearly
ready,
> whitelisting is essential to us.
>
> Please advice,
>
> Jan
>
> On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary <
>
>
>
> taylorsinglet...@twitter.com
<mailto:taylorsinglet...@twitter.com>> wrote:
> > Sorry Adam, missed this document among the many -- it's fixed
now. The form
> > itself and its text are immutable at the moment.
>
> > On Sat, Feb 12, 2011 at 5:26 AM, Adam Green <140...@gmail.com
<mailto:140...@gmail.com>> wrote:
>
> >>http://dev.twitter.com/pages/rate-limiting#whitelisting
>
> >> Ryan, Taylor, Matt, I know changing mistakes in the docs has been
> >> impossible in the past. My guess is that someone lost the
password for
> >> these pages. But leaving the whitelisting statement in the
docs and
> >> the whitelisting form online is a sign of complete disrespect
for your
> >> developers. New devs will see this and still think they can get
> >> whitelisting. Even worse they will waste their time building
apps that
> >> need whitelisting, since the request form says:
> >> "Whitelisting is only available to developers and to
applications in
> >> production"
>
> >> How would you feel if you started building an app today, spent
months
> >> on it, got it into production, and then waited months for
approval,
> >> since the docs say you won't get a response until approval is
done?
>
> >> Not removing this shows that developers don't really matter to
> >> Twitter. Removing it right away shows that they do. Please
don't say
> >> that you are too busy to make that change, and that it will be
done
> >> some time in the future. Nobody is that busy.
>
> >> Please remove 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 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
