We’ve had a number of requests from the Wesabe community for more detailed information about what the Wesabe development team is working on. We’re going to address these requests in a few separate steps, and today we’re introducing the first of those steps.
Wesabe’s Twitter account has been a very popular way to get Wesabe news and money-related links. (We were even featured recently in O’Reilly’s Twitter for Business report as a great example of a business using Twitter.) We’ve also had a very enthusiastic response to our Twitter integration, which lets you add transactions to your Wesabe accounts. We’ve decided to keep going with our Twitter successes by introducing a new Twitter account for people interested in more frequent, detailed updates from our development team.
The new account is called WesabeUpdates. Following this new Twitter account will get you updates every time we deploy a new version of the site, and detailed messages about what’s going into those updates. Basically, this is to Wesabe’s blog the same thing Twitter usually is to blogs: a quicker, more frequently updated account that gives you what you want in very short messages.
To ensure we’re getting the detail people have asked for, we’ve set up a direct connection between our development chat room and this Twitter account, so any developer can easily add an update to the account. (By the way, we also just open-sourced our Campfire bot framework, Wesabot, written by the unstoppable Brad Greenlee, with small contributions from most of the Wesabe team. The framework has a bunch of plugins, including the Twitter update plugin.)
Update: For those of you who don’t use Twitter or don’t want to use it for this purpose, we’ve added the three most recent WesabeUpdates posts to our Accounts index page (the page you see when you first log into Wesabe). Take a look in the left column, below your account links. Also, the idea for showing the number of developers contributing to a deploy of the site was shamelessly stolen from the good people at Flickr. I first saw the idea on their Flickr Code site. Thanks, Flickreenos!