Separate calls might be bad because twitter would have to put up with http requests. OTOH if assembling all of that information is expensive then separate might work too.
On Mar 25, 5:55 pm, JakeS <jakesteven...@gmail.com> wrote: > That event query does sound like a great idea. I wouldn't even mind > if each one of those was a separate call. > > On Mar 25, 3:22 am, Seth Ladd <sethl...@gmail.com> wrote: > > > I'd also love to see an event log. That would help my application > > tremendously, and would seemingly address any syncing use cases. > > > On Mar 24, 4:36 pm, Bill Robertson <billrobertso...@gmail.com> wrote: > > > > I would like to see an event query. > > > > Request: user id, since (date only) > > > Response: > > > notification if user's profile has changed > > > id's of deleted messages (in timeline, not just owned by user) > > > ids or details of new followers for user > > > ids of lost followers for user > > > ids of details or new followings for user > > > is of lost followings for user
