I would like to hear a response from Twitter on the sharing of this data. My db has about 2 million active users, and I have another db with 6 million or so I would gladly share.
Previously I think the response from Twitter is that they cannot provide this as a bulk translation due to the demand it would place on their servers. They are able to provide the entire list of follower IDs simply because that lives in memory and requires no joins. The joining to get this data would be too intensive for them. If this is allowed maybe the community could take this a step further and provide a common interface to share data like this. Any thoughts? On May 31, 1:42 pm, Dan Brickley <[email protected]> wrote: > On 31/5/09 13:03, Stuart wrote: > > > Since there's clearly a lot of demand for this feature is it not > > possible for it to be added to the official API? I'd hesitate before > > building anything on top of Twitter that also relies on a third party > > for something so basic. > > Related suggestion: have common REST API for external services who can > provide this information. You can probably get it from google social > graph API too, for example. > > Dan
