the process of changing up the codebase to use id_str in anticipation of
Snowflake. One popular design decision we have made is to interleave
sent and received direct messages into one unified list. Currently, we
sort by message ID to figure out which message comes before the other.
Since JS cannot parse the new 64bit integers, we can no longer do this.
The only way I see to do this under Snowflake is to sort based on
created_at, is that a valid approach? Is there a better way to approach
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: