I was agreeing with you that there is value here and that it hasn't been brought up in conversation.
Users have asked for a way to know when to stop paging through @replies and the count value would alleviate some of the concerns I've seen on this board over the current "iterate-until-you-step-off-the- end" method of finding the last page. Additionally, a cached count value is understandably valuable in it's own right, which is why the other two timelines have it. In my first response, by user_timeline I meant friends_timeline. But thinking a little harder I realize that this number could be of little real world use for most users so you can ignore my mumbling. In other news, I'd like you to move forward with the request, because it's a feature I could use. On Jan 15, 11:37 am, "Chad Etzel" <[email protected]> wrote: > On Thu, Jan 15, 2009 at 11:20 AM, dougw <[email protected]> wrote: > > > Chad, > > I haven't seen anything of the sort but since @replies are just > > another user specific timeline, perhaps the issue is more with a > > "count" value being returned with each user timeline over just this > > specific timeline. > > Can you rephrase that? I'm afraid I didn't understand that sentence at all :( > > > > > There has been quite a few discussions that would have been alleviated > > (pagination, etc...) that would have been resolved if every user > > timeline were returned with a count value as well. I can see the value > > extending this idea to all user timelines, can you? > > user_timeline already does support "count". so does friends_timeline. > Even though it isn't explicitly stated, it seems to be working with > sent and received direct message calls as well. Just seemed odd to me > that Replies didn't have it. > > -Chad > > > > > @dougw > > > On Jan 15, 9:35 am, "Chad Etzel" <[email protected]> wrote: > >> I see that the current Replies API call does not support a "count" > >> parameter. I will open an issue for this, but wanted to double check > >> this hadn't been discussed/submitted before even though I searched the > >> issues and group archives. > > >> -Chad
