All that Twitter needs to do to solve this problem is to build the
JSON out with next_cursor and previous_cursor as string values.

I.e., the JSON data should contain:

"next_cursor":"12398712981212987","previous_cursor":"-12398712981212987"

I don't know what it will do to Java apps, but for PHP apps it will
solve the problem.

Dewald

Reply via email to