For anyone else out there who has code or services integrated with Twitter, you should take a look at this soon.
The Twitpocalypse is similar to the Y2K bug. Very soon the unique identifier associated to each tweet will exceed 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.
Time to haul out some BigInt action.
Every time we re-work the user interface for Tempo (we’re now upon our third major overhaul), the same thing happens and it doesn’t take long: I can’t stand to use the old/current interface any longer. The new design by nGen Works is no exception, it totally blows away the last iteration, and I think we’ve very nearly nailed down all the nuts and bolts.
I’m really excited to start the beta and get some of our customers’ feedback. A big thanks to those of you who wrote in asking to participate! We just have some administrative details to take care of and we should be rolling soon. If you’d like to participate in the beta and this is the first you’re hearing of it, just send us an e-mail.
A couple things of note:
We recently received reports of duplicate tags in Tempo. Turns out that it was possible to submit a tag with leading or trailing white-space from the batch-tagging interface, and this could cause the creation of a new, unwanted tag. This has been repaired and shouldn’t be a problem in the future. We ripped through the database and repaired incidences of this, but if you need us to make any other corrections to your account data, don’t hesitate to ask.
We’ve been working really hard on a redesigned interface for Tempo. Our friends over at nGen Works put together a fantastic new design, and we’ve been working it in and testing it over the last few weeks. We have a few more bugs and quirks to iron out, but we’re about ready to start the beta testing. If you want to participate in the beta, please send us an e-mail and we’ll let you know when you can have at it!
We did it! The initial version of Strip has made it into the iTunes App Store, along side Strip Lite, a free version with a 10-record limit.
Strip is a password manager and data vault for the iPhone. It relies on SQLCipher for data storage – it’s our own build of SQLite that provides military-grade encryption of the entire database using the OpenSSL library. If you want to dig deeper, we have more information on the product site, and the SQLCipher page.
To check it out, download Strip Lite or take the tour.
Take a tour of the app if you’re still not convinced it rocks.
STRIP stands for “Secure Tool for Recalling Important Passwords.” STRIP first appeared for PalmOS mobile devices in 1997 and grew to be one of the highest rated, award winning security applications for the platform for over 12 years. This is a ground-up rewrite for the iPhone platform featuring improved usability and enhanced security. Thus, we’ve changed the name to “Strip”.
We discontinued STRIP’s development a couple of years ago due to the decline in the Palm OS platform. We’ve since added the source to Github for anyone who wants to take up the cause themselves. As we previously mentioned here, we will be providing a migration path to the iPhone version for Palm users ASAP, as well as updating strip-dump to support users moving to other platforms and software.
We’d like to extend our thanks to the many beta testers who helped us put together an excellent product. Extra special thanks goes out to nGen Works for designing Strip’s new identity, logo, and badge. Last but not least, the various articles and tips on Mobile Orchard, including a post on how to avoid app rejection, have been enormously helpful.
