Hi Taylor, Thanks for your quick reply, that's everything I needed to know!
Niels On Sep 1, 4:57 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Niels, > > Our whitelisting system still operates almost exclusively on IP address and > "accounts" -- not applications. So yes, once you move to using OAuth for > your account, it will be given the same whitelisted limits. You can more > quickly implement your single access token example by making use of the "my > access token" feature on dev.twitter.com that will provide the access token > for the user who owns the application without having to bother with the > entire OAuth request cycle. > > Taylor > > On Wed, Sep 1, 2010 at 7:54 AM, Niels van der Rest > <n.vanderr...@gmail.com>wrote: > > > > > Our application never has to make API requests on behalf of the end- > > user. We don't even call API methods that require authentication. > > That's why we haven't implemented OAuth. > > > However, we did make the requests on behalf of a white-listed account > > using Basic Authentication, to benefit from the 20,000 calls/hour rate > > limit. If we were to use the single access token-approach, we'll have > > to register an application first in order to generate the access > > token. > > > Will this application or access token be white-listed automatically if > > the application is registered using the white-listed account? > > > -- > > 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?hl=en -- 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?hl=en