<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mashable - The Social Media Guide - Latest Comments in Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.disqus.com/</link><description>Internet and Technology News - Mashable is the world’s largest blog focused exclusively on Web 2.0 and Social Networking news. With more than 5 million monthly pageviews, Mashable is the most prolific blog reviewing new Web sites and services, publishing breaking news on what’s new on the web.</description><atom:link href="https://mashable.disqus.com/twitpocalypse_ii_twitter_apps_might_break_tomorrow/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 22 Sep 2009 17:24:25 -0000</lastBuildDate><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17146284</link><description>&lt;p&gt;Well, looks like Twittelator Pro didn't survive intact.  No longer refreshes properly but instead takes you back to the time of failure forcing you to scroll back to the present to see your lastest updates&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Orion</dc:creator><pubDate>Tue, 22 Sep 2009 17:24:25 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17122285</link><description>&lt;p&gt;News #FAIL.&lt;br&gt;How not to write something that you don`t have enough knowledge.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lucas Arruda</dc:creator><pubDate>Tue, 22 Sep 2009 12:41:18 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17108591</link><description>&lt;p&gt;Fie on your integers and bits. It's just that some apps will be taken up in the Rapture.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sally</dc:creator><pubDate>Tue, 22 Sep 2009 05:15:26 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17108576</link><description>&lt;p&gt;Fie on your integers and bits. It's just that some apps will be taken up in the Rapture.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sally</dc:creator><pubDate>Tue, 22 Sep 2009 05:14:26 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17104891</link><description>&lt;p&gt;I realize they don’t have direct control over 3rd party apps, but back when the Twitter devs were aware of the first oncoming twitpocalypse, why didn’t they just make the first post-twitpocalypse tweetID something larger than you could fit in a 32-bit unsigned int?? 2^32+1. Problem solved, now where’s *my* millions in venture capital!?!?&lt;/p&gt;&lt;p&gt;This would have forced 3rd parties to adopt 64-bit tweetid’s months ago. But no, here we are again. Sometimes I think Twitter employees really dig failure.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jeux video</dc:creator><pubDate>Tue, 22 Sep 2009 02:03:36 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17070728</link><description>&lt;p&gt;Why not just make it 4,000,000,000,000 and save the developers the hassle . . . or would that add more hassle . . . I probably wouldn't be asking this question if I was a developer.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Foodie</dc:creator><pubDate>Mon, 21 Sep 2009 20:27:44 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17068313</link><description>&lt;p&gt;Of course, but is that plenty of time for Apple to approve the applications! lol. Sorry, just hating since I dropped the iPhone like a bad habit.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">barkerja</dc:creator><pubDate>Mon, 21 Sep 2009 19:14:25 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17068291</link><description>&lt;p&gt;Hey Ben, this upcoming 'Twitpocalypse' is actually caused by the 32-bit unsigned integer limit, not the 64-bit integer limit. The previous Twitpocalypse was for 32-bit signed integers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Thomson</dc:creator><pubDate>Mon, 21 Sep 2009 19:13:53 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17068239</link><description>&lt;p&gt;This was announced back at the &lt;a href="http://groups.google.com/group/twitter-api-announce/browse_frm/thread/8f7f1b3cef846f98?hl=en" rel="nofollow noopener" target="_blank" title="http://groups.google.com/group/twitter-api-announce/browse_frm/thread/8f7f1b3cef846f98?hl=en"&gt;end of July&lt;/a&gt;. That's plenty of time for iPhone app developers to update their Twitter applications.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Thomson</dc:creator><pubDate>Mon, 21 Sep 2009 19:12:03 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17068033</link><description>&lt;p&gt;The only true Twitpocalypse is twitter itself and all the idiocy around it, including it's engineers.&lt;/p&gt;&lt;p&gt;It has nothing to do with 32bit vs 64bit integers - those numbers listed as limits are signed vs unsigned 32 bit integers. 64bit unsigned upper limit is 9,223,372,036,854,775,807.&lt;/p&gt;&lt;p&gt;Perhaps knowing how to use an application on the internet aside from twitter would be valuable when writing an article.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">HZ</dc:creator><pubDate>Mon, 21 Sep 2009 19:06:27 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17067530</link><description>&lt;p&gt;OH!&lt;br&gt;Ok. Thanks. Haha, I'm not good with computer stuff. Thank you! :D&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kera Torrence</dc:creator><pubDate>Mon, 21 Sep 2009 18:53:39 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17067071</link><description>&lt;p&gt;Dude, Ben.   64 bits is not 4,294,967,296.&lt;/p&gt;&lt;p&gt;If 32 bits == 2,147,483,647,   doubling that number only adds one additional bit of significance.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Name</dc:creator><pubDate>Mon, 21 Sep 2009 18:42:19 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17066910</link><description>&lt;p&gt;change what? you don't need to change anything, only if you have a twitter client that you developed YOURSELF then you have to be sure the IDs are handled with large numbers than 64 bit integers, maybe you can use strings to handle them or whatever you find suitable for this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Mon, 21 Sep 2009 18:37:34 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17066749</link><description>&lt;p&gt;Wait how do I change it? Or how do I check what my ID thingy is??? O.o&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kera Torrence</dc:creator><pubDate>Mon, 21 Sep 2009 18:33:41 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17066705</link><description>&lt;p&gt;wooo, I wonder who will post the tweet that will cause the twitpocalyse? that would be a legend :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Mon, 21 Sep 2009 18:32:38 -0000</pubDate></item><item><title>Re: Twitpocalypse II: Twitter Apps Might Break Tomorrow</title><link>http://mashable.com/2009/09/21/twitpocalypse-ii-update/#comment-17066693</link><description>&lt;p&gt;God help you if an iPhone Twitter app needs a last minute update!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">barkerja</dc:creator><pubDate>Mon, 21 Sep 2009 18:32:20 -0000</pubDate></item></channel></rss>