That is a design decision we leave up to the application developer. So long as you aren't storing credentials (OAuth applications never do) then we are happy campers.
It makes sense for a lot of Twitter applications to use the Twitter user id as the application's internal account id. However it can make growing difficult if the service will move to support other services other than Twitter. When developing an application that will likely support more than one service, a level of indirection (application dependent user ids) would be recommended. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 9:08 AM, Arik Fraimovich <[email protected]> wrote: > > On Apr 13, 10:37 pm, Matt Sanford <[email protected]> wrote: > > It is currently the case that you will get the Accept/Deny page > > every time. We're working on a redirect like Zachary mentioned and > > hope to have it out by the end of the week. > > Is this kind of usage you will encourage or is it still be better to > create our own user login system? > > Thanks > Arik >
