This would be VERY useful to us. Although for our needs, a stream might be overkill. But if each request for the social graph data can come with a request ID, or even an exact time stamp, which we could provide on the next request and get a diff between the two calls, it would help a lot.
If either a stream or a diff is available, it'd need to include both new followings and new unfollowings. -Joel On Jun 10, 8:47 pm, Doug Williams <[email protected]> wrote: > There has been discussion of pushing social graph changes through the > streaming API in much the same way that Dewald has requested. At this time > there is nothing to report nor a definitive decision on if it will ever be > publicly available. > I know Jesse's use case from an earlier thread but are there any others to > augment our internal discussions? > > Thanks, > Doug > > On Wed, Jun 10, 2009 at 5:13 PM, Jesse Stay <[email protected]> wrote: > > I've proposed this with Alex before, but yes, this would be very useful to > > me. > > Jesse > > > On Wed, Jun 10, 2009 at 4:00 PM, Dewald Pretorius <[email protected]>wrote: > > >> Currently all of us are using the delta between a certain follower > >> social graph snapshot and a subsequent follower social graph snapshot > >> to figure out who are the new followers of an account. > > >> When doing follower processing, all one really is interested in is the > >> fact that a new follower action has occurred. > > >> To me, this sounds like a perfect pub-sub candidate. > > >> Now here's what I was thinking. > > >> Gnip.com can already segment data by person, keyword, etc. It should > >> fit into their model to segment transactions by Twitter screenname. > > >> So, if Twitter can push every new follower transaction to Gnip, and us > >> developers can subscribe on Gnip to the follower transactions of > >> specific users, I think we have a win-win situation on our hands. > > >> Twitter has to push every transaction out once only to one > >> destination, they don't have to carry the pub-sub infrastructure and > >> load, and us developers can get follower transactions that don't > >> affect our site rate limits. > > >> Thoughts? > > >> Dewald
