Well, there's two bits that could be causing problems - Twitter's API, or the module isn't _quite_ right with their new API changes.

If you're wanting to do something fairly straightforward, can you just hook straight into twitter? https://dev.twitter.com/docs/using-search

I've just tried clicking through their example URLs, but it hasn't worked. But that might be a reasonable start point - after all, you can then just stick together using 'LWP'. I think that might be because (according to some quick and dirty googling) API 1.1 is now fussier about authentication.

If you try opening: https://api.twitter.com/1.1/search/tweets.json?q=nyc - do you get a 215 'bad authentication' error like I do?