<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>iMore &#187; twitpocalypse</title>
	<atom:link href="http://www.imore.com/tag/twitpocalypse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.imore.com</link>
	<description>More of everything iPhone and iPad</description>
	<lastBuildDate>Sun, 27 May 2012 13:54:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Twitpocalypse Now&#039;ish -- Is Your iPhone Twitter Client Safe?</title>
		<link>http://www.imore.com/2009/06/13/twitpocalypse-nowish-iphone-twitter-client-safe/</link>
		<comments>http://www.imore.com/2009/06/13/twitpocalypse-nowish-iphone-twitter-client-safe/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 13:12:14 +0000</pubDate>
		<dc:creator>Rene Ritchie</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[twitpocalypse]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[twitter client]]></category>

		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=9156</guid>
		<description><![CDATA[<a href="http://www.imore.com/images/stories/2009/06/picture-101.png"></a>

<a href="http://www.twitpocalypse.com/">Twitpocalypse.com</a> defines the event as:

<blockquote>
  similar to the Y2K bug. The unique identifier associated to each tweet has now exceeded 2,147,483,6471 [...] For some of your favorite third-party Twitter services </blockquote>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.imore.com/images/stories/2009/06/picture-101.png"><img src="http://www.imore.com/images/stories/2009/06/picture-101-400x190.png" alt="picture-101" title="picture-101" width="400" height="190" class="aligncenter size-medium wp-image-9157" /></a></p>

<p><a href="http://www.twitpocalypse.com/">Twitpocalypse.com</a> defines the event as:</p>

<blockquote>
  <p>similar to the Y2K bug. The unique identifier associated to each tweet has now exceeded 2,147,483,6471 [...] For some of your favorite third-party Twitter services not designed to handle such a case, the sequence will suddenly turn into negative numbers. At this point, they are very likely to malfunction or crash.</p>
</blockquote>

<p>Here's how it may be affecting some of your favorite iPhone Twitter clients:</p>

<ul>
<li><strong>Tweetie:</strong> Official word: <a href="http://twitter.com/atebits/status/2153788845">Searches are busted</a>, hoping to update soon.</li>
<li><strong>Birdhouse:</strong> Updated: Publishing is fine, unpublishing is broken. Fix is on its way.</li>
<li><strong>Twitterrific:</strong> Currently experiencing problems after a preventative update wasn't enough to avoid the great doom. Second update in the works per <a href="http://iconfactory.com/home/permalink/2129">Icon Factory</a>.</li>
<li><strong>Twitterfon:</strong> Unknown, if you have word, let us know.</li>
<li><strong>Twittelator Pro:</strong> <a href="http://twitter.com/twittelator/status/2148509411">Claims to be okay</a> (thanks @JNHohol for the link!).</li>
<li><strong>Twitkitteh</strong>: Is, apparently, <a href="http://twitter.com/jamesthomson/status/2152574842">unaffected</a>.</li>
</ul>

<p>If you notice your favorite Twitter client misbehaving, drop a comment below or let us know via <a href="http://twitter.com/theiphoneblog/">@theiphoneblog</a> and we'll update.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.imore.com/2009/06/13/twitpocalypse-nowish-iphone-twitter-client-safe/feed/</wfw:commentRss>
		<slash:comments>30</slash:comments>
		</item>
	</channel>
</rss>

