I'm getting the same issue -
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/3c13f89ac3c5a945.Still
without any solution :(

2010/10/4 timrnicholson <timrnichol...@gmail.com>

> Well, I thought i had this problem solvIed. I am using a library called
> twitteroauth and it was stripping off the "&include_rts=true". I
> finally figured out that include_rts needed to be placed into an
> arguments array instead of being in the request URL.
>
> So once I got the include_rts parm passed to Twitter everything was
> working fine. Or at least it was in most cases. HOWEVER, I am seeing
> now that certain requests are NOT returning the full count parameter
> worth of records. There must be SOME filtering that the Twitter API is
> doing AFTER it retrieves the count number worth of records. I have
> this problem regardless of whether I use the home_timeline which is
> supposed to always include everything or whether I use the
> friends_timeline with the include_rts parameter.
>
> Note that I am trying to request count = 25 records, not the default
> count = 20 records. I can see that retweets are being included and I'm
> still getting ust 24 records back in certain cases.
>
> On Sep 9, 10:06 am, Matt Harris <thematthar...@twitter.com> wrote:
> > Hey Tim,
> >
> > When I run:
> >     curl "
> http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page...";
> >
> > I get the expected result of 20 statuses one retweet (from
> > @ConanOBrien). When you make the request are you running it like I am
> > or are you using a library?
> >
> > To answer your query about thecountparameter. The behavior is this:
> > we will try and return up to 'count' statuses in one request,
> wherecountis equal to all statuses in the timeline before any filtering of
> > retweets. So, if you request 20 statuses without retweets, and 1 of
> > the statuses is a retweet, you will get 19 statuses back.
> >
> > Hope that helps explain what is going on,
> > Matt
> >
> >
> >
> >
> >
> > On Thu, Sep 9, 2010 at 7:30 AM, timrnicholson <timrnichol...@gmail.com>
> wrote:
> > > I'm properly calling api.twitter.com/1/statuses/user_timeline with
> > > include_rts as true and retweets arenotbeing included. The only
> > > stream that I can get to return retweets (because it doesn't even
> > > require the include_rtsparameter) is the home_timeline.
> >
> > > For example, the following doesn't work:
> > >http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page.
> ..
> >
> > > The worst part about this isnotjust that the include_rtsparameter
> > > 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 isnotonly ignoring the include_rtsparameterbut itsnot
> > > 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, thecountparameteris 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 <taylorsinglet...@twitter.com>
> > > wrote:
> > >> Hi Timmerk,
> >
> > >> Make sure you're using api.twitter.com as the host for all of your
> API
> > >> requests. The proper API isnotat twitter.com -- it's at
> api.twitter.com.
> > >> Include_rts willnotwork 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 <timm...@gmail.com> 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 <thematthar...@twitter.com> wrote:
> > >> > > Hey Hen,
> >
> > >> > > Are you still finding retweets arenotshowing up for you?
> >
> > >> > > Matt
> >
> > >> > > On Sat, Aug 21, 2010 at 7:19 AM, henasraf <doku...@gmail.com>
> wrote:
> > >> > > > Matt,
> > >> > > > Any user I show in my app wouldnotshow 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;youmay 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 <thematthar...@twitter.com>
> 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?
> > >> > > >> Ifnotcould you give an example of a username which shows this
> > >> > problem.
> >
> > >> > > >> Best,
> > >> > > >> Matt
> >
> > >> > > >> On Thu, Aug 19, 2010 at 1:24 PM, henasraf <doku...@gmail.com>
> 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-Hidequoted
> > >> > 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-Hidequoted
> > >> > 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
> >
> > --
> >
> > 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
>



-- 
Pozdrawiam,
Michał Łowicki

-- 
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

Reply via email to