<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: maxint</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/maxint.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-06-09T10:52:38+00:00</updated><author><name>Simon Willison</name></author><entry><title>The Twitpocalypse is Near: Will Your Twitter Client Survive?</title><link href="https://simonwillison.net/2009/Jun/9/twitpocalypse/#atom-tag" rel="alternate"/><published>2009-06-09T10:52:38+00:00</published><updated>2009-06-09T10:52:38+00:00</updated><id>https://simonwillison.net/2009/Jun/9/twitpocalypse/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.programmableweb.com/2009/06/09/the-twitpocalypse-is-near-will-your-twitter-client-survive/"&gt;The Twitpocalypse is Near: Will Your Twitter Client Survive?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Twitter tweet IDs will shortly tick over past the maximum signed 32 bit integer, potentially breaking applications. I learnt this lesson when the same thing happened to Flickr photo IDs: never store numeric IDs from external systems as integers, always use strings.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apis"&gt;apis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/flickr"&gt;flickr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ids"&gt;ids&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/maxint"&gt;maxint&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="apis"/><category term="flickr"/><category term="ids"/><category term="maxint"/><category term="twitter"/></entry></feed>