Filed under: Analysis / Opinion, Software, Bugs/Recalls, iTunes, Apple, Developer, App Store
Twitpocalypse aftermath and "incident" fixes on the App Store
I didn't really take last week's Twitocalypse that seriously, but as you probably know by now, it turned out a little worse than expected -- we'd been told that Twitterrific (and, we assumed, most other Twitter apps) would be fine, and of course, as Craig Hockenberry explains on his blog, things ended up not-so-fine. Desktop app developers, of course, could publish updates as quickly as they could code them; iPhone developers were in a different situation.When the Iconfactory's app stopped working, most people (including me) got an API error all weekend. Craig found the bug, then he and his team were able to leverage their contacts at Apple Developer Relations to help expedite the release; in short order, an update was pushed out to the App Store. I downloaded it yesterday, and can tell you that things are fixed... at least until the numerical limit on Twitter's tweet identifier raises its head again (or the Newton flips out, but that's another story).
Hockenberry also has ideas about how to keep issues like this from happening again. Not the actual issue of a variable overflow (that will undoubtedly happen again at some point, on Twitter or any other API that scales way faster than anyone expects it to), but the issue of iPhone apps needing a quick fix. He says that Apple should give every developer a number of "incidents" -- situations rarely used, in which a high priority fix can get sent out to apps in major emergencies. He says, and it's true, that for most developers, it's not a question of if you'll need to send out a critical fix, it's a matter of when. And support by Apple, obviously limited to one or two instances per developer, would help developers, distributors, and consumers.
Of course, it's up to Apple, and it's not like they've smoothed out the approval process so well already that they can start adding wrinkles to it. But clearly, given that the Twitterrific update went through quickly, there's room for exceptions to be made.
[via DF]
If you've been having issues with corrupted Time Machine images either inside the Time Capsule or connected externally to your base station, the 
There has been plenty of confusion over the continuing saga of Seagate hard drives with firmware problems that can lead to eventual failure and data loss. We've followed the story 
As 30GB Zune owners deal with the 
There's a lot of "could" and "might" in this story, folks, so keep that in mind. MacNN is reporting that a group of iPhone developers has identified a bug in the current iPhone firmware that could lead to an exploit of the Default.png file. 
How long is two weeks? If you're vacationing someplace warm and sunny, it might seem to pass in a flash; if you're in bed with the flu, it probably seems like a lifetime. For Office 2008 users who 
TUAW reader John T. alerted us to an issue with Sprint's SmartView application, version 1.85.0007.0. 
It has been a 
Apple Insider is reporting that 
Users of Linotype FontExplorer X may want to hold off on the 10.5.2 update ... if it's not already too late. It seems to start up fine, but once you do, clicking a stack will cause the Dock to hang; that's just one symptom, there are problems reported with several applications crashing while FontExplorer X is running. 
Now this is just getting silly. Apparently there is a bug with the iPhone where if you try to automatically sync more than eight ringtones up, 
Despite Keynote's maturity, 
AppleHound has posted a list of 
![TUAW [Cafepress]](http://www.blogsmithmedia.com/www.tuaw.com/media/tuaw-cafepress-promo.png)
