I know it’s been a while since I was supposed to be fixing the issues with TweetBomb. I’ve been a bit busy with the day job and the kids getting ready for back to school, so I haven’t had much time (read: none at all) to devote to it. Sorry for the delays. I’ve figured out what the cause of the issue was, at least. It looks like during the DDoS attacks that Twitter was suffering lately, their API (understandably) became somewhat unreliable. Unfortunately, the way I had the queue system set up, I didn’t handle broken API results properly and it hosed the entire queue.
I’m going to be re-working the entire back-end portion of the system over the next couple of days. Now that the children are back in school, I’ll probably have more time to work on it. When all is said and done, there will be no more queue. Once you submit your Twitter credentials, the system should start deleting your old tweets almost immediately. I’ll let everyone know when it’s back up and running properly.
Also, I got whitelist approval from Twitter for the app, so it should no longer go against your personal API request limit for the hour. This means that you won’t have to worry about TweetDeck (or your other Twitter client of choice) being unable to keep up with your Twitter stream because you run out of API calls.
Again, sorry for the delays. Look for news soon.