This is awesome... Thank you..

Will start playing with your suggestion.

Best,
Randolph


On Nov 30, 2:59 am, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> statuses/followers and statuses/friends don't require authentication and are
> likely subject to this condition. When calling these resources, are you
> explicitly providing the user_id or screen_name?
>
> These methods are some of the oldest offered in the API and aren't really
> the best choices for consuming data of that nature. You would be better
> positioned to use friends/ids and followers/ids in conjunction with
> users/lookup
>
> Taylor
>
> On Mon, Nov 29, 2010 at 10:54 AM, m36tb6ll <raeste...@gmail.com> wrote:
>
> > Thanks for the reply, Taylor...
>
> > Are the API requests "statuses/followers" and "statuses/friends"
> > included in the "public-only" resources that you are referring to? Or,
> > I'm I not making any sense? :)
>
> > Randolph
>
> > On Nov 30, 2:19 am, Taylor Singletary <taylorsinglet...@twitter.com>
> > wrote:
> > > There are some API methods that don't have the concept of an
> > unauthenticated
> > > user -- these "public-only" resources will not consider OAuth credentials
> > > when calculating the rate limit. We are looking to make the application
> > of
> > > rate limiting across resources, regardless of whether the resource
> > expects
> > > auth or not, consistent in the future.
>
> > > Taylor
>
> > > On Mon, Nov 29, 2010 at 10:05 AM, Randolph Estebat <raeste...@gmail.com
> > >wrote:
>
> > > > Thanks for the reply, Igor...
>
> > > > Yes it should be. The problem is that the headers are giving me the
> > limit
> > > > 150 rather than the expected 350 after OAuth.
>
> > > > Any ideas why this is the case?
>
> > > > Thanks again.
>
> > > > On Mon, Nov 29, 2010 at 8:17 PM, Igor Kharin <igorkha...@gmail.com>
> > wrote:
>
> > > >> All rate limited methods responses include X-Ratelimit-Remaining and
> > > >> X-Ratelimit-Limit HTTP-headers, use them or
> > > >>http://dev.twitter.com/doc/get/account/rate_limit_status
>
> > > >> On Fri, Nov 26, 2010 at 1:55 PM, m36tb6ll <raeste...@gmail.com>
> > wrote:
>
> > > >> > Hi! I am a newbie in the field and am working on my first twitter
> > web
> > > >> > app. I have created a variable loop timer using rate_limit_status
> > > >> > which works well in maximizing the usage of the twitter API without
> > > >> > going over the hourly limits.
>
> > > >> > Now that I have incorporated OAuth, I was expecting to see the limit
> > > >> > increase from 150 (unauthenticated requests) to 350 (authenticated
> > > >> > requests). But, I am still seeing the 150 limit both in the response
> > > >> > headers and Firebug when calling rate_limit_status API after OAuth.
>
> > > >> > Is there something I'm missing here?
>
> > > >> > Your help would be greatly appreciated. Thanks in advance...
>
> > > >> > --
> > > >> > 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
>
> > > > --
> > > > Randolph Estebat
>
> > > > --
> > > > 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

Reply via email to