[twitter-dev] Single sign-on - One oauth for a mash-up

[Swan]

Scenario
 - TwitterAppA has an oAuth
 - TwitterAppA has as part of its functions an embed from TwitterAppB
which also uses Twitter oauth

The goal is for users to be able to oauth with TwitterAppA and then be
recognized automatically as the same user by the embed of
TwitterAppB.  Without this the user gets quite confused as they don't
understand why they have to login multiple times on one site.

Allowing for that functionality would allow all the TwitterApps to
begin working in concert to meet user needs which makes the whole
community far more effective.

I realize though that it does open the door for some security
problems.  However, it seems that Twitter could maintain a graph of
which apps were embedding which other apps in order to allow a trusted
relationship model.

[twitter-dev] batch API calls

[Swan]

I have been whitelisted.  We are currently developing our caching
strategy.

We store Twitter user information for the hosts of events that we get
from the user.xml API call.   We would like to refresh our cache daily
to update the follower/following info as well as any possible Bio,
Name, or photo changes in Twitter.

Will Twitter care if we do a large batch all at one time as long as we
are not hitting the API throughout the day?
Also, if we do the batch, at what time of day does Twitter API have
the lowest traffic for us to do our update?

Thx for the help,
Swan