when dealing with retrieving a large followers list from API, what i
did was estimate the no. of pages i need (total / 5000) from the
follower count of user's profile, and then send concurrent API
requests to improve the speed.
now with the new cursor-based pagination, this become impossible(it
Not lately but on Sept 9 I see this in our logs.
URL
http://twitter.com/account/verify_credentials.json
HEADERS
Expect:
Authorization: OAuth realm=http://twitter.com/account/
I haven't switched to the cursor method yet but I access the follower
list like you described and I have no issues with performance since
the calls aren't serialized. If the reliability could be fixed and
the page parameter preserved, then I'd vote for that.
On Sep 18, 1:09 am, alan_b
Pretty much the same behavior with followers/ids and statuses/
followers:
http://code.google.com/p/twitter-api/issues/detail?id=1033colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
This one was reported on 9/13, and the status is still New.
Hi,
I have my ip whitelisted so it should get 2 request per hour.
The point is that when i login in with my username to my twitter
application hosted on the specified IP - i get all the 2 requests
per hourbut if i login with a different user name - i get only
150.
My question is -
Hello again,
I'm sorry for posting a follow up so soon, but I spent another few
hours trying to debug this again last night, and still without
success. It seems to be encoding the characters properly (%65E5%672C
%72AC in this case), and so I assume it is generating the signature
properly. After
Yep, that did the trick. Thanks, Abraham. I'll look into updating
the example on the API wiki.
Cheers,
-Rob
On Sep 17, 2:21 pm, Abraham Williams 4bra...@gmail.com wrote:
That cURL command is resulting in a GET when a POST is required. Try adding
-d with an empty string.
curl -u
The page based approach does not scale with large sets. We can no
longer support this kind of API without throwing a painful number of
503s.
Working with row-counts forces the data store to recount rows in an O
(n^2) manner. Cursors avoid this issue by allowing practically
constant time access
Mageuzi wrote:
I'm sorry for posting a follow up so soon, but I spent another few
hours trying to debug this again last night, and still without
success. It seems to be encoding the characters properly (%65E5%672C
%72AC in this case), and so I assume it is generating the signature
properly.
Hi Alan,
I originally thought this was a show-stopper too, but it can be worked
around by simply processing multiple accounts using those threads
rather than multiple pages of a single account.
Something like this:
Have a producer that emits the account IDs requiring update onto a
queue,
The Retweet API launch is close at hand. You might have already seen
some retweets appearing in the new statuses/home_timeline from people
who've been testing them out. We've gotten lots of great questions and
feedback about the retweet API. Thanks to everyone who has rolled up
their sleeves and
Hi Rob (and Abraham),
Thanks for finding that omission. I have updated the wiki to include
the blank post parameter.
-Chad
On Fri, Sep 18, 2009 at 8:26 AM, Rob Hutten r...@hutten.org wrote:
Yep, that did the trick. Thanks, Abraham. I'll look into updating
the example on the API wiki.
Hello,
Are you absolutely sure that outgoing requests from your server are
coming from the same IP you whitelisted? You will see an increased
rate-limit on your personal account because that is the account you
used to apply for whitelisting, so it will always have an increased
limit no matter
On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote:
Asking developers to collapse retweets in timelines is onerous,
complicated and confusing. We're not going to do it that way. We are
going to add a resource that gives you all retweets for a given tweet.
In timelines
The Streaming API took about 15 minutes of unscheduled downtime today
at about 21:30 UTC. All should be back to normal now.
We can deal w/ rate limiting, just give us some semblance of accuracy
or the calls are pointless.
Excactly, my main point, too.
The problem is I want to track how tweets 'develop' over time. This
means I would need to pull the status/retweets every minute or so for
every tweet I am tracking. There is a 150 api call limit currently...
without whitelisting I will be doomed.
I was hoping that
Marcel Molina wrote:
To give you some ideas of how you can use the API to display retweets,
here is a recent mock up of one of the potential UIs for the retweets
timeline on twitter.com:
http://a1.twimg.com/example-retweet-ui-18-sep-09.png
In this example, how did you retrieve the number and
The blocks/blocking method appears to be similar to the statuses/
friends and statuses/followers methods, but I believe the
documentation is incomplete for all three.
According to the API spec, each call to statuses/friends and statuses/
followers returns a page of up to 100 users (and their
19 matches
Mail list logo
