Direct Message IDs will become Snowflake-based 64-bit integers on Friday, September 30th.
Today, I am writing to inform you that we’ll begin using Snowflake for direct message IDs beginning one week from today, on September 30, 2011. This transition cannot be delayed or waylaid and we apologize in advance for any inconvenience this may put on applications not already utilizing the string-based identifier representations or relying on 32-bit integers.
If you’re already storing & utilizing the “id_str” value as a string, there shouldn’t be any action required on your part. It is still most advisable to sort by an object’s created_at date rather than relying on the identifiers as having any kind of meaning — however, Snowflake IDs are generated in such a way that you should have little to no issues sorting by ID.
If you have any questions or concerns, please follow up on the discussion forums.
Thank you for your attention to this very important announcement.
The @twitterapi Team