Twitter’s Snowflake Project To Update Tweet IDs Really Is More Like A Blizzard Now
Last week, we noted that Twitter was on the verge of executing their long-in-the-making Snowflake project. Basically, this was a necessary step to switch up the way tweet IDs are handled due of Twitter’s move from MySQL to Cassandra for their database infrastructure. Twitter clearly realized that the switch-over might be a little bumpy, and that’s why they started alerting third-party developers about it months ago. But it turns out it’s even more bumpy than they realized. And that’s why the transition hasn’t happened yet. And won’t for a while.
Luckily, you have some more time. Harris notes that this coming Friday (October 22), they will start placing string versions of tweet IDs in the API. On November 4, the plan is then to activate Snowflake, but limit tweet IDs to 41 bits. But on November 26, these IDs will go longer than 53 bits, so you’ll need to have your updated code in place by then.
[photo: flickr/sarah ackerman] [thanks Alex]
- Tweet IDs About To Get Jumbled In A Blizzard As Snowflake Is Set To Roll Live
- Twitter Is Now The Proud Owner Of Re-tweet.com
- Twitter For Mac’s Spectacular Hidden Little Feature: Tweet Anything From Anywhere
- Twitter’s Year In Review Begins With A Tweet Tree
- International Longest Tweet Contest Seeks Entries