Hmm this is strange. Also Twitter REST API Method: statuses/update does not have rate limited. Does this mean we can allow an authenticated twitter user to post as many updates to Twitter from our website as he/she wants?
Or am I not understanding this correctly? On Jul 3, 6:29 pm, Christian Fazzini <christian.fazz...@gmail.com> wrote: > Hmm ok just found out that verify_credentials is not rate limited. So > I guess we can log as many users on without limitations... > > Correct me if I am wrong. > > On Jul 3, 5:22 pm, Christian Fazzini <christian.fazz...@gmail.com> > wrote: > > > Hello, > > > We are developing a website that uses the Twitter API. At current, > > when a users gets onto our site, a login screen appears, prompting the > > user to enter his/her twitter username and password. Our system/ > > website doeshttp://twitter.com/account/verify_credentials.format > > (http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ra... > > ) to check if this is a valid user and if their password and username > > match. If we get a '200' code then we log the user. > > > However,http://apiwiki.twitter.com/Rate-limitingsays: > > "The default rate limit for calls to the REST API is 150 requests per > > hour. The REST API does account- and IP-based rate limiting. > > Authenticated API calls are charged to the authenticating user's limit > > while unauthenticated API calls are deducted from the calling IP > > address' allotment." > > > Does this mean that we can only get 150 users > > requestinghttp://twitter.com/account/verify_credentials.formatata given > > hour? > > > Are we doing our logon process correctly this way? Or should we > > consider a better approach to this?