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
