currently there are a lot of shortcuts in get_users - make them better
don't have these set - at least think these through. (they all need better names)
limit - the number to return
num_to_use - the number of the supplied input users to use (probably doesn't make sense in this context
count_from_twitter - the number of users to retrieve from twitter
min_num_mutual_relations - this doesn't make sense in the context, but some sort of score might make sense - maybe min_score?
The _insert_into_graph_if_not_present function and deeper functions all the way down to _get_relations_from_twitter are a little weird.
They require ids or screen_names but we will only have screen names now. (Though it might be worth keeping ids around in case they are required later.)
The "friends" vs "followers" argument is sloppy and it's always hard to figure out what is meant by these terms.
the hydrating portion of get_users is really sloppy because I'm just rerunning the big painful query again - and the only reason for this is to regroup the users. To fix this, make hydrate_users respect grouping.
currently there are a lot of shortcuts in get_users - make them better
limit- the number to returnnum_to_use- the number of the supplied input users to use (probably doesn't make sense in this contextcount_from_twitter- the number of users to retrieve from twittermin_num_mutual_relations- this doesn't make sense in the context, but some sort of score might make sense - maybemin_score?_insert_into_graph_if_not_presentfunction and deeper functions all the way down to_get_relations_from_twitterare a little weird.get_usersis really sloppy because I'm just rerunning the big painful query again - and the only reason for this is to regroup the users. To fix this, make hydrate_users respect grouping.