As far as I can tell, there has been no progress on this.  There is a
bug open for the issue, if you would like to follow it:
http://code.google.com/p/twitter-api/issues/detail?id=1264


On Jan 9, 8:30 am, bear <bea...@gmail.com> wrote:
> I am now seeing this on some of my own accounts - has any movement or
> fix been applied?
>
> here is the url i'm trying:
>
> curlhttp://twitter.com/statuses/friends/codebear.json  <-- returns
> []
> curlhttp://twitter.com/statuses/friends/manta.json      <-- returns
> {"request":"/statuses/friends/manta.json","error":"Not found"}
>
> On Dec 28 2009, 2:42 pm, Mageuzi <mage...@gmail.com> wrote:
>
> > Sorry to keep bringing this up, but this is still causing problems for
> > me.  Is there any follow-up as to what the issue is?  Thanks in
> > advance.
>
> > On Dec 22, 10:06 pm, Mageuzi <mage...@gmail.com> wrote:
>
> > > Is there an update to the status of this issue? A user of my program
> > > reported a problem that ended up being this.  While trying to iterate
> > > through:http://api.twitter.com/1/statuses/friends/oevl.xml
> > > Cursor 1274505087418535016 returned fine and contained a next_cursor
> > > value of 1267920196862230269.  That value returned a 404.
>
> > > On Dec 8, 1:32 pm, Ammo Collector <binhqtra...@gmail.com> wrote:
>
> > > > If you get the following URLs and continue to using the next_cursor,
> > > > you receive incorrect 404s:
>
> > > >http://twitter.com/statuses/friends/debra_bee.xml?cursor=130554434315...
>
> > > > Any ideas?

Reply via email to