Also applications that support multiple twitter accounts will probably have to have their own local user authentication system, unless anyone has figured out a better way to deal with this?
-Chad On Tue, Apr 14, 2009 at 3:27 PM, Doug Williams <[email protected]> wrote: > 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 >
