You will need these if you're working with ImageFields in Django.
A solid (and maybe better) replacement for Twitter tracking.
It's not as real-time as the original tracking, but that's kind of a nice thing as you can opt to check for your updates hourly or daily, and you don't get a million text messages all day long. You can also add links to your search, which are gathered in real-time; Tweetbeep will even find links that have...Ok son, put the Twitter down and back away slowly...
Twitter sent some downtime notices today via a regular friends_timeline JSON request. Even though the downtime is a bummer, this kind of error reporting is really nice, as you aren't left with that "should I keep refreshing the page?" feeling.
Often Twitter crashes return full XHTML pages to API calls, like the "Too many tweets!" page with the whale that we've been seeing lately. These aren't parsed into a Twitter feed like this error message was (API rate limit notices and other errors are returned as valid JSON though). This can be worked around by looking at the HTTP code that is returned, but I wish there was some way for the app to return valid JSON error messages to API requests instead of the default XHTML crash pages.
Leave comments on this blog, or let's talk on Twitter or Facebook.
Tags: twitter, downtime, maintenance, error reporting, itweet
WebKit's new JavaScript interpreter may improve performance for the iPhone.
And our tumultuous relationship with the Bluebird of Happiness/Crappiness...
Twitter has decided to remove a certain call from their API that the iTweet 2 private beta relied on to create the "ticker" effect that kept it updating at nearly real-time speeds. The rate limit for API calls also remains handicapped, cut to 30 per hour from the usual 70. This makes using Twitter API tools extremely inconvenient, and developing them is also quite frustrating.
For now I have removed the "ticker" feature and the friends timeline will refresh every 140 seconds, though this number may be adjusted slightly as I attempt to keep the page open and in use today. (Big thanks to all my helpful beta testers for your excellent feedback on the last iTweet 2 development cycle!) Further development on the beta will continue when the API rate limit returns to normal. Until then, Twitter API development is a waste of time as most people seem to be ditching API apps for the non-limited Web site.
This is actually a good thing for me, as I am working hard on developing some other tools for The Illusion Factorythat I will be posting more about soon. Apologies for the lack of updates recently, I've been...