Voting starts in March for the Drupal Association Board election.
Twitter's API v1 was retired on June 11th 2013 but the current stable version of this module does not support Twitter API v1.1, which requires authenticated connections using OAuth.
Various solutions to this have been discussed here. The main question is whether to use the Twitter and OAuth modules to connect to Twitter, to use an external library, or to include that code in this module.
Current status, as of June 28th 2013:
If you DO want to use the Twitter and OAuth modules
This is the way this module is going. In due course, a stable release will be available with this.
For D6: Use the latest stable (6.x-1.4) with the patch in #107
For D7: Use the latest 7.x-2.x-dev, with the Twitter and OAuth modules installed and configured as described in #73, even though Twitter Pull doesn't list them as dependencies yet.
If you DON'T want to use the OAuth and Twitter modules
This is NOT the path this module's maintainers have chosen. If you choose this option, you are affecting your ability to upgrade your copy of this module in future. However, it looks like a fork of Twitter Pull that takes this path is under development.
Download this library: https://github.com/J7mbo/twitter-api-php
Put it in ../libraries/twitter-api-php/TwitterAPIExchange.php
For D6: use latest stable (6.x-1.4) and the patch at #41
For D7: use latest stable (7.x-1.0-rc5) and the patch at #76
Is this module going to stop working when Twitter turn off the old (version 1) API and require OAuth for everything?
That'll be in 6 months time, if I read it right.