[twitter-dev] Re: Getting any users home timeline

[Dharmesh Parikh]

Would appreciate some feedback on this?
sorry for resending.

--dharmesh



On Fri, Sep 4, 2009 at 12:07 PM, dp dharmesh.par...@gmail.com wrote:


 So the statuses/friends_timeline api call gives an authentated users
 and his friends statuses. Basically that authentacted users home
 page.

 Now is there any similar way to get any users home timeline.  statuses/
 user_timeline gives the statuses for any user specified by a userid.
 But it gives what is posted by them only.

 An e.g to clear things up

 User X is authenticated through API.
 the App makes a call and gets his home timeline using statuses/
 friends_timeline .

 User X has a friend User Y.  App can call statuses/user_timeline  for
 user Y but that will return only User Ys statutes (which can also be
 got from statuses/friends_timeline  earlier).

 What i want is an easy way so the the App can get User Y;s home time-
 line ( User Ys statuses as well User Y friends statuses).

 One can find User Ys friends and then call statuses/user_timeline for
 each of friend to get what i want. Seems to expensive in terms of api
 calls

 Any better way of doing this? i could not see the api supporting this
 directly.

 --dharmesh




-- 
--Dharmesh

[twitter-dev] Re: Pagination limit for REST API(3200)

[Dharmesh Parikh]

So if i user_timeline REST api call and use max_id =X  or since_id = Y and
count=200 i can get 3200 messages backwards from X or 3200 messages forward
from Y and then hit the limit.

My specific questions:
1) can i use some different max_id and count=200 after the above scenario is
hit.

2) What if in the next user_timeline REST api calls i use a different
reference point max_id = A or since_id = B can i use count=200 and still get
different set of 3200 messages?


--dharmesh



On Tue, Aug 4, 2009 at 12:34 AM, Josh Roesslein jroessl...@gmail.comwrote:

 Correction: 3200--1800
 Sorry for that math error ;)


 On Mon, Aug 3, 2009 at 2:03 PM, Josh Roesslein jroessl...@gmail.comwrote:

 I believe it means you can not go back more than 3200 statuses.
 Example:
   user has posted 5000 statuses. you can only view statuses 3200+ via the
 api.

 Its not a limit that gets used up like the api rate limit.


 On Mon, Aug 3, 2009 at 1:39 PM, dp dharmesh.par...@gmail.com wrote:


 Hi Doug,

 I did read that but was not able to get the exact implications of it,
 thats why the question.

 So lets say i use count to get 3200 messages in history for a user,
 then can i use the count ever again (count 20), or i have reached the
 limit for that user permanently??


 -dharmesh

 On Aug 3, 10:28 pm, Doug Williams d...@twitter.com wrote:
  Hi there --
  Check out #6 in the Things Every Developer Should Know article [1].
 
  1.https://apiwiki.twitter.com/Things-Every-Developer-Should-Know
 
  Thanks,
  Doug
 
  On Sun, Aug 2, 2009 at 11:27 AM, dp dharmesh.par...@gmail.com wrote:
 
   When the REST API limit for using count/page reaches 3200 for a
   particular user account, does it mean that that user account can
 never
   use count/page parameters any-more??
 
   Does this limit reset?




 --
 Josh




 --
 Josh




-- 
--Dharmesh