• [Feature]: When you go to retweet an official retweet, it doesn't look like a chain retweet any more so you get a better feel of what is happening.
• [Feature]: We now support tweet entities for timeline and mentions. This means that when Twitter switch on t.co for all tweets, Twitterfall will match what Twitter.com displays.
• [Feature]: We now support expanding goo.gl addresses
• [Bug]: When you click to logout of Twitterfall, the login button now reappears properly.
• [Bug]: When loading lists (subscribed or own) if there is a failure the text changes back from 'Loading...' like it should (thanks Ben)

As you may know, Twitterfall has supported global exclusions for some time. This means that you can filter out spammers, or certain terms (e.g. 'free xbox'). Now we've gone one step further to help you filter your Twitterfall.

You can now exclude services from your Twitterfall.

To do this, simply add 'service:badservice' to your exclusions. You can see what services tweets come from by viewing them on Twitter.com.

Today we have pushed out a brand new version of Twitterfall for iPhone. Not only has it been completely rewritten from the ground up, but it also has plenty of new features. In particular:

• It now supports multiple accounts (timeline, mentions, and tweeting), and multiple searches.
• It's lightning fast to load, and because it's been completely rewritten scrolling is super- smooth, even on an iphone 3G.
• Tapping on a hashtag shows you a preview of some tweets containing that hashtag.
• Persistent view of tweets when you close the app.
• The same great Twitterfall-style timeline view.

We've designed the Twitterfall app to do what you normally use Twitter for really well, rather than adding loads of unnecessary features. Huge thanks to Mike Tomasello for working with us to bring our iPhone app up to date!

Check it out on the App Store, available for just 59p ($0.99), where you will find screenshots and some more information.

Let us know what you think!

• The Twitter API is slow. At peak times it can take seconds, not milliseconds, to respond. As a result, we have to run lots of PHP processes on our server that have to sit maintaining connections, using up lots of memory (This isn't what PHP was designed for!). When Twitterfall first started, this used to be a huge problem, now it's more of a niggling pain, but still there.
• The PHP code is basic, it doesn't forward errors to the client (it just silently fails), and is very difficult to debug. It's been around since the start of Twitterfall, so understandably it's got a bit long in the tooth.
• There's no easy way of monitoring it, and adding monitoring to an already bulky process would just slow it down more. 

So we've worked on a replacement, and we're pleased to say it's been running in production successfully now for quite some time. We've built it on several great components available:

• Erlang, which is great at running hundreds, thousands, even millions of concurrent processes, great for the slow Twitter API.
• Mochiweb, a lightweight HTTP server framework for Erlang that powers Facebook Chat, and Hydrometeor.
• erlang-oauth, an Erlang library for dealing with oAuth requests. We have modified it to support:
• ibrowse, an HTTP client written in Erlang that replaces Erlang's HTTP client, which we've experienced big problems with when dealing with multiple concurrent requests to the same server.
• erlang-collectd, an Erlang library for logging data to collectd, a monitoring daemon.

This means: 

• We can handle loads of concurrent connections to Twitter without breaking a sweat.
• We can easily monitor the status of the connection between Twitterfall and Twitter, which makes it easier to inform our users when Twitter have a problem (and they think it's us).
• We can monitor how people use Twitterfall to help improve the user experience.
• Twitterfall feels more responsive.

Thanks to this new component, we've made the following observations: 

• The Twitter API errors a lot. Sometimes it will return 404 errors on known API endpoints for no apparent reason, and quite often it will return capacity errors.
• The Twitter API is really slow when America are awake. Here's a graph of response time when people have made authenticated requests to the Twitter API via Twitterfall:
   
• People have lists in their Twitterfall that don't exist any more, so we've added a visual cue to show when you have a list in your Twitterfall that doesn't exist.
• People don't notice their tweets are too long, so we've made it so that you are warned if you try to send a tweet that is more than 140 characters.

Other updates

• Fixed a bug with loading your lists.
• Fixed a bug that caused the geolocation map that shows up for geolocated tweets to stop working.
• Added some new error messages.

We've also made a few tweaks to Twitterfall, the main one being:

Improved URL shortening

Now, if you shorten a URL in the 'New Tweet' box it will shorten the URL and add the title of the web page you are linking to (when possible). (yeah, the example above is bad, but you get the idea!)

Other changes

• We've moved the @ symbol out of Twitter links to stay consistent with the Twitter user interface.
• We've adjusted some of the default colours to improve readability.
• You can now view tweets in conversations between protected users if you are following those users.
• We've added a '?present=' URL parameter which allows you to set the presentation mode text immediately when the page loads. This was at request from @bennuk.
• We've improved some of our Javascript. Source 1, Source 2 (avoiding eval() with YUI Compressor), Source 3.
• We've fixed the bug with DMs not working.