Well here's my answers:
On Mon, Jun 8, 2009 at 11:15 PM, Doug Williams d...@twitter.com wrote:
Jesse,
Please submit an issue if you feel that this would contribute to the
community. There are issues for paging bugs with the social graph methods so
star them appropriately.
Will do - I like
Doug, et. al., here's the problem(s) I'm running into. By forcing me to use
paging for followers/ids and friends/ids, for someone like BritneySpears I
now have to make over 350 requests to get through all her followers. Now
I'm having huge rate limit issues because of that, not to mention how
I'll share are a few other wrinkles I've observed in the paged
friends / followers API responses:
- There are often more (sometime many more) pages than you'd expect
based on the follower/friend counts listed in the profile
- Pages in the middle of a long series of output pages usually but not
Jesse,
Please submit an issue if you feel that this would contribute to the
community. There are issues for paging bugs with the social graph methods so
star them appropriately.
I have some questions to the community at large using the social graph
methods so please feel free to chime in:
What
I've heard that list sizes greater than 150K-200K start to return timeouts
at higher rates. Although I'd enjoy hearing first-hand experiences and
recommendations.
Thanks,
Doug
On Wed, Jun 3, 2009 at 9:19 PM, Jesse Stay jesses...@gmail.com wrote:
In my case specifically it's the Social Graph
Yes, that's what appears to be happening. My experience starts at around
500K+. I'm okay with waiting with my script if you guys need to take longer
to retrieve the info. Or if you'd prefer we paginate I'll start doing that
as well. Maybe a hard limit of 200K and you have to Page to get above
Also, how do you recommend we deal with the larger users that would like to
follow back their followers? With the hard limit of 1,000 follows per day,
there is no way they'll ever catch up, as some of them have more than 1k new
followers per day as is. If this limit were more dynamic based on the
We would like users to be judicious with their following habits and only
follow users who contribute value to their timeline. This justifies the
following limits we impose.
We are aware that many users would like to accept all incoming directs.
This, along with the quid pro quo following to build
On Thu, Jun 4, 2009 at 1:23 PM, Doug Williams d...@twitter.com wrote:
We are aware that many users would like to accept all incoming directs.
Sounds like a checkbox in your profile to me.
Sean, why not let the users decide that though? If I enable the option for
my account it's my responsibility to weed out the spam. If I don't want the
spam then I won't enable it on my account. Giving users multiple options is
a good thing.
Jesse
On Thu, Jun 4, 2009 at 2:31 PM, Sean Scott
Jesse,
If the implementation is to make that a preference which is turned off by
default (no DM by non followers) that users can toggle, then i am totally
for it. As you point out its then the users responsibility to clean their
inboxes if they get hit by spam after turning the feature on.
So
What methods in particular are you referring to? The social graph methods
now support paging so retrieving all of that data is now possible, where it
used to throw 502s. It does however require a bit of application logic to
assume when paging is necessary (e.g. large follower counts).
In my case specifically it's the Social Graph methods. I didn't realize you
had paging available now. Is there some logic as to when I should expect to
page and when I can just rely on the full result?
Jesse
On Wed, Jun 3, 2009 at 9:56 PM, Doug Williams d...@twitter.com wrote:
What methods in
13 matches
Mail list logo
