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.
Created in 2006, Twitter is a global real-time communications platform with 400 million monthly visitors to twitter.com, more than 200 million monthly active users around the world. We see a billion tweets every 2.5 days on every conceivable topic. World leaders, major athletes, star performers, news organizations and entertainment outlets are among the millions of active Twitter accounts through which users can truly get the pulse of the planet.