[twitter-dev] Re: statuses/friends page count?
On Jul 6, 9:09 pm, Doug Williams wrote: > You should either page through statuses/friends until you get an empty > response set or use statuses/show to get the number of friends expected and > intelligently page to the end of the list. Ok, thank you, so it's the 'official' method. But I am still curious, can't all friends on a page be filtered out? -- Dmitriy V'jukov
[twitter-dev] statuses/friends page count?
Hi! It's unclear how I must determine how many pages retrieve via statuses/ friends. First guess was to fetch until I will retrieve page with 0 friends. However documentation says that there can be arbitrary number of friends per page because of the "filtered out" friends. So I guess I can receive page with 0 friends just because there are all filtered out. Or you will handle such case internally and never send me a page with 0 friends? What is the "official" way? Also my bet that pages start at 1, but I think it's worth adding into docs. Thank you. -- Dmitriy V'jukov
[twitter-dev] Re: [OAuth] GET parameters
On May 12, 10:40 pm, Matt Sanford wrote: > Hi there, > > The parameters should be required for the OAuth signature. Can > you please provide the request and response headers for an example? Hi Matt, Forget about that nonsense, the fault was on my side. Now works as expected. When I've tried to collect headers and all other debug info, I've noticed that GET parameters was just not appended to the URL. So actual URL was http://twitter.com/statuses/friends_timeline.xml, not surprisingly that you did not include my GET parameters into signature calculation :) -- Best regards, Dmitriy V'jukov
[twitter-dev] [OAuth] GET parameters
Hi! I do following request: http://twitter.com/statuses/friends_timeline.xml?since_id=1773396714&count=20 When I include GET parameters (since_id, count) into OAuth signature calculation I am getting HTTP 401 error. However when I do NOT include GET parameters into OAuth signature calculation request succeeds. So I guess, you are just excluding GET parameters from OAuth signature calculation on your side. AFAIS, this is against OAuth spec. Is there any plans for fixing this? As on option you may support both variants for some time to not break old clients instantly. Or I am just missing something? Thank you. -- Best regards, Dmitriy V'jukov
