404 Errors on friends and followers using cursors

[Ammo Collector]

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=1305544343158947280
http://twitter.com/statuses/followers/fraying_ends.xml?cursor=-1
http://twitter.com/statuses/followers/Sabrinita_Linda.xml?cursor=-1

Any ideas?

[Randy]

I am seeing the same issue. In my case, the first four iterations work
(i.e. I retrieve 400 users), but the next call gives me a 404.

[Randy]

I added this to the issue tracker: http://code.google.com/p/twitter-api/issues/detail?id=1264

[Randy]

I added this as issue 1264 in the twitter-api issue tracker, which
you'll have to find on your own. It appears they don't trust me enough
to let me post links here yet. :D

On Dec 8, 1:01 pm, Randy <randy.posyn...@gmail.com> wrote:

[John Kalucki]

Over the last 4 or so days there has been a few brief periods of instability on the backing store that provides the Social Graph. I'd re-run your test to see if you were just very unlucky, or if the issue persists.

-John Kalucki

http://twitter.com/jkalucki

[Randy]

I am still seeing this issue. Trying the URLs provided by Ammo
Collector in the top post still yields 404's as well.

On Dec 9, 9:50 am, John Kalucki <j...@twitter.com> wrote:
> Over the last 4 or so days there has been a few brief periods of instability
> on the backing store that provides the Social Graph. I'd re-run your test to
> see if you were just very unlucky, or if the issue persists.
>

> -John Kaluckihttp://twitter.com/jkalucki

[Mark McBride]

I can verify the issue, looking into it...

--
---Mark

http://twitter.com/mccv

[Ammo Collector]

Another one: http://twitter.com/statuses/friends/giannetti.xml?cursor=1311765355356921547

On Dec 8, 10:32 am, 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...http://twitter.com/statuses/followers/fraying_ends.xml?cursor=-1http://twitter.com/statuses/followers/Sabrinita_Linda.xml?cursor=-1
>
> Any ideas?

[Mageuzi]

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

[Mageuzi]

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?

[bear]

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:

curl http://twitter.com/statuses/friends/codebear.json <-- returns
[]
curl http://twitter.com/statuses/friends/manta.json <-- returns
{"request":"/statuses/friends/manta.json","error":"Not found"}

[Mageuzi]

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

[Shannon Whitley]

I've been hitting this a lot lately with data for my own id. It's a
huge issue. I'm happy to see that it's been marked as a high
priority, but it's been around for months. Do we have an estimate for
a fix? Thanks!

[Mark McBride]

Very soon.

  ---Mark

http://twitter.com/mccv

[Mark McBride]

And by soon I mean today.  It should be fixed now.  Let me know if this recurs.

  ---Mark

http://twitter.com/mccv