[twitter-dev] Re: User_Timeline - include_rts not working

2010-09-09 Thread Mike Francisco


timrnicholson wrote:
> I'm properly calling api.twitter.com/1/statuses/user_timeline with
> include_rts as true and retweets are not being included. The only
> stream that I can get to return retweets (because it doesn't even
> require the include_rts parameter) is the home_timeline.
>
> For example, the following doesn't work:
> http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page=1&include_rts=true
>
> The worst part about this is not just that the include_rts parameter
> doesn't work for including retweets, the returned timeline doesn't
> even have 20 records in it when there are retweets. In other words,
> the API is not only ignoring the include_rts parameter but its not
> even returning the right number of requested records when it thinks
> include_rts is false.
>
> This totally screws up my pagination methods because I'm getting less
> than the expected number of records back, so my app thinks there's no
> more timeline to be retrieved. I certainly don't want to just always
> include a "next page" link when there really aren't any more records
> left.
>
> Also, the count parameter is being ignored in all of this as well, but
> I've latched on to another thread about that.
>
> On Aug 30, 12:50 pm, Taylor Singletary 
> wrote:
> > Hi Timmerk,
> >
> > Make sure you're using api.twitter.com as the host for all of your API
> > requests. The proper API is not at twitter.com -- it's at api.twitter.com.
> > Include_rts will not work against twitter.com (and one day you'll find all
> > of your requests rejected.)
> >
> > Also, please note that proper API routes include a version component. The
> > call you're making should 
> > be:http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWa...
> >
> > Taylor
> >
> >
> >
> > On Mon, Aug 30, 2010 at 10:43 AM, timmerk  wrote:
> > > I'm having the same issue - you can see an example here:
> >
> > >http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOV&;...
> >
> > > As you can see, there are no retweets included in the JSON.
> >
> > > Thanks!
> >
> > > On Aug 25, 2:30 pm, Matt Harris  wrote:
> > > > Hey Hen,
> >
> > > > Are you still finding retweets are not showing up for you?
> >
> > > > Matt
> >
> > > > On Sat, Aug 21, 2010 at 7:19 AM, henasraf  wrote:
> > > > > Matt,
> > > > > Any user I show in my app would not show retweets, even if they surely
> > > > > exist. You can see for yourself athttp://wosaic.net/twitguin(still
> > > > > early stages, don't mind it being a bit lame), see any user such as
> > > > > myself athttp://wosaic.net/twitguin/user/henasraf;you may go
> > > > > through pages and see that no retweets ever show; they should be color
> > > > > coded in orange. You can compare tohttp://twitter.com/henasraftosee
> > > > > retweets that should show.
> >
> > > > > Thanks,
> > > > > Hen
> >
> > > > > On Aug 19, 11:34 pm, Matt Harris  wrote:
> > > > >> Hey,
> >
> > > > >> Retweets should be included if they exist in the users timeline when
> > > you
> > > > >> request them. For example if you request 20 Tweets of the timeline 
> > > > >> and
> > > one
> > > > >> of those last 20 was a retweet - it will be included. If one of the
> > > last 20
> > > > >> Tweets wasn't a retweet it won't be included, even if include_rts is
> > > true.
> >
> > > > >> Does this explain what is happening in your app?
> > > > >> If not could you give an example of a username which shows this
> > > problem.
> >
> > > > >> Best,
> > > > >> Matt
> >
> > > > >> On Thu, Aug 19, 2010 at 1:24 PM, henasraf  wrote:
> > > > >> > Hey all, I'm using user_timeline to fetch the timeline of a user in
> > > my
> > > > >> > app. Problem is, it doesn't include native Retweets, even though
> > > I've
> > > > >> > set include_rts to true. The docs clearly say it should work, but 
> > > > >> > it
> > > > >> > doesn't. What could be the problem? Thanks in advance :)
> >
> > > > >> --
> >
> > > > >> Matt Harris
> > > > >> Developer Advocate, Twitterhttp://twitter.com/themattharris
> >
> > > > --
> >
> > > > Matt Harris
> > > > Developer Advocate, Twitterhttp://twitter.com/themattharris-Hide quoted
> > > text -
> >
> > > > - Show quoted text -
> >
> > > --
> > > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > > API updates via Twitter:http://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >http://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >http://groups.google.com/group/twitter-development-talk?hl=en- Hide quoted 
> > >text -
> >
> > - Show quoted text -

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


Re: [twitter-dev] Re: Change in error response objects

2010-08-30 Thread Mike Francisco


Raffi Krikorian wrote:
> it is designed so that we can send multiple error codes back, but in
> practice, right now, we only send one.
>
> On Sun, Aug 29, 2010 at 4:25 PM, Dewald Pretorius  wrote:
>
> > Raffi,
> >
> > Will the new error construct always be:
> >
> > [errors][code]
> > [errors][message]
> >
> > Or can it be sometimes:
> >
> > [errors][0][code]
> > [errors][0][message]
> > [errors][1][code]
> > [errors][1][message]
> >
> > --
> > Twitter developer documentation and resources: http://dev.twitter.com/doc
> > API updates via Twitter: http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> > http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> > http://groups.google.com/group/twitter-development-talk?hl=en
> >
>
>
>
> --
> Raffi Krikorian
> Twitter Platform Team
> http://twitter.com/raffi

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en