[twitter-dev] Re: Developing Group Management Add-On for TweetDeck
Hi Bob What functionality would the group management tool provide? Would you be able to send tweets directly to a group, for example? Isn't that functionality already in tweetdeck? I'm confused. --Joe On Sun, May 10, 2009 at 10:41 AM, subbob sub...@gmail.com wrote: I've been considering the usefulness of a Group Management application for TweetDeck. This application would directly manipulate TweetDeck's SQLite database. The application would address the following problem: Each time you create a group using the TweetDeck interface, the user selection panel shows everyone you follow. I'd rather see a list of those not already assigned to a group, so that as I create groups, that list shrinks until it is empty. (i.e. everyone is assigned to one group or another) Prior to starting this project, I wanted to see if anyone else is already working on something like this, or perhaps already has developed such a tool? Also, has anyone developed other applications that directly interfaced with TweetDeck's SQLite database?
[twitter-dev] Re: [Q] how to collect info on followers efficiently
Thanks Cameron, thats what I need, until I get to 500K followers :) On Fri, May 8, 2009 at 7:27 AM, Cameron Kaiser spec...@floodgap.com wrote: Let's say I want to write an application that operates a twitter account X, and I want the application to obtain every hour for each follower Y of X to obtain the count of followers of Y (how many, not the actual list). I know I can do this via the followers.xml API but that (a) returns only 100 of X's followers at a time, and (b) returns a LOT of data I don't need. Have you looked at the social graph methods? These are still paged, but at 5000/page. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- A zebra cannot change its spots. -- Al Gore -- FleshJoe a href=http://www.fleshjoe.com/fleshfiles/index1.html;Still using your hand?/a
[twitter-dev] Re: [Q] how to collect info on followers efficiently
Unfortunately these APIs give you the IDs of your followers, but not the number of followers that each of these IDs has. So this is not the answer. Ordinarily I'd write my app to cache the IDs of the twitter account that it's operating so that it would not have to ask for this list every time. Basically I want the following: [for all Y where Y is a follower of X | Y, the number of followers of Y] So it looks like I'm limited to the status methods which return 100 results at a time, and whose return info contains the info I need. I'm guessing I'll just have to apply for whitelisting once X gets more than 10K followers. On Fri, May 8, 2009 at 7:27 AM, Cameron Kaiser spec...@floodgap.com wrote: Let's say I want to write an application that operates a twitter account X, and I want the application to obtain every hour for each follower Y of X to obtain the count of followers of Y (how many, not the actual list). I know I can do this via the followers.xml API but that (a) returns only 100 of X's followers at a time, and (b) returns a LOT of data I don't need. Have you looked at the social graph methods? These are still paged, but at 5000/page. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- A zebra cannot change its spots. -- Al Gore
[twitter-dev] [Q] how to collect info on followers efficiently
Let's say I want to write an application that operates a twitter account X, and I want the application to obtain every hour for each follower Y of X to obtain the count of followers of Y (how many, not the actual list). I know I can do this via the followers.xml API but that (a) returns only 100 of X's followers at a time, and (b) returns a LOT of data I don't need. Yes, within that data for each follower of X there is the info I need, but this is very wasteful way of obtaining the data. And since twitter rate-limits applications to only 100 API calls per hour this would not work when account X has more than 10K followers. So what are my options? Thanks, --Joe
