And by soon I mean today. It should be fixed now. Let me know if this
recurs.
---Mark
http://twitter.com/mccv
On Tue, Mar 9, 2010 at 6:54 PM, Mark McBride wrote:
> Very soon.
>
> ---Mark
>
> http://twitter.com/mccv
>
>
> On Tue, Mar 9, 2010 at 5:02 PM, Shannon Whitley > wrote:
>
>> I'v
Very soon.
---Mark
http://twitter.com/mccv
On Tue, Mar 9, 2010 at 5:02 PM, Shannon Whitley
wrote:
> 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
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!
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 wrote:
> I am now seeing this on some of my own accounts - has any movement or
> fix be
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.jso
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 wrote:
> Is there an update to the status of this issue? A user of my program
> reported a problem that ended up being this
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.
Another one:
http://twitter.com/statuses/friends/giannetti.xml?cursor=1311765355356921547
On Dec 8, 10:32 am, Ammo Collector 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=13
I can verify the issue, looking into it...
On Wed, Dec 9, 2009 at 12:33 PM, Randy wrote:
> 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 wrote:
>> Over the last 4 or so days there has bee
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 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-
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
On Tue, Dec 8, 2009 at 1:40 PM, 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 wrote:
> I am seeing the same issue. In my case, the first four iterations work
> (i.e. I retrieve 4
I added this to the issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1264
On Dec 8, 1:01 pm, Randy wrote:
> 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.
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.
14 matches
Mail list logo
