Hi Mark,

These fields were added in January 2010 to address the problem when the
cursors were too long for javascript to handle. The original announcement is
on our API Announce list [1] and there are no plans to remove this

Hope that helps,


On Fri, Jul 23, 2010 at 8:45 AM, Mark Krieger <markskrie...@gmail.com>wrote:

> I found that statuses/friends and statuses/followers have an
> undocumented field called next_cursor_str and prev_cursor_str, which
> are simply the string values of those fields in addition to the digits
> passed back in next_cursor and prev_cursor. Is this planned to stay
> this way? (can I rely on them always being in the api?)
> I was working around a known json_decode bug on 32-bit machines on one
> of our test portables, where it could not decode the next_cursor, no
> big deal, but when I found the 'str' versions of the cursors I turned
> off the workaround. Once $id's get large enough, 32-bit machines will
> need json_decode to work right too....so the workaround might be
> needed then.
> Mark


Matt Harris
Developer Advocate, Twitter

Reply via email to